CVE-2026-94192 Module object deallocation can free a live ThreadX kernel object
HighCVSS 8.5
EPSS 0.15%
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: total
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| Eclipse Foundation Eclipse ThreadX | >= 6.0.1, <= 6.5.1.202602a | after 6.5.1.202602a | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Eclipse Foundation Eclipse ThreadX | >= 6.0.1, <= 6.5.1.202602a | No fix listed |
References
- github.com
- ENISA EUVD EUVD-2026-105144 third-party-advisory