CVE-2026-94192
A ThreadX module allocates the control blocks of its kernel objects from the Module Manager's…
- Risk score
- 52/100
- CVSS
- 8.5 v4.0
- Exploit chance (30 days)
- 0.1%
- Published
- 20 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 o…
- Affected
- See advisory
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 8.5 high
References
Original 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.
Last activity 20 Oct 2026. Patch Forecast updates every hour.