Vulnerability Description
A ThreadX module allocates the control blocks of its kernel objects from the Module Manager's object pool, and can ask for that memory back by address with `txm_module_object_deallocate`. The manager released it whatever was in it, including a control block the kernel was still using. Deallocation is not deletion: the object stays on the created list for its type, a thread stays wherever it was on the ready or suspension lists and stays schedulable, and an active timer stays on the timer list. The byte pool is meanwhile free to hand those same bytes to the next allocation.
Related Weaknesses (CWE)
References
FAQ
What is CVE-2026-94192?
CVE-2026-94192 is a documented vulnerability. A ThreadX module allocates the control blocks of its kernel objects from the Module Manager's object pool, and can ask for that memory back by address with `txm_module_object_deallocate`. The manager ...
How severe is CVE-2026-94192?
CVSS scoring is not yet available for CVE-2026-94192. Check NVD for updates.
Is there a patch for CVE-2026-94192?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.