{"id":"CVE-2026-94023","published":"2026-10-20T16:17:17.763","lastModified":"2026-10-20T19:48:50.250","description":"A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex.\n\n\n\nDestroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":["CWE-125","CWE-862"],"vendors":[],"products":[],"references":[{"url":"https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-36vf-7cx6-9f9j","tags":[]}],"exploitRefs":[{"url":"https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-36vf-7cx6-9f9j","tags":[]}],"hasPoc":true,"ai":null}