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.
Destroying 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.
CVSS
No CVSS.
References
Configurations
No configuration.
History
20 Oct 2026, 16:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-20 16:17
Updated : 2026-10-20 19:48
NVD link : CVE-2026-94023
Mitre link : CVE-2026-94023
CVE.ORG link : CVE-2026-94023
JSON object : View
Products Affected
No product.