CVE-2026-94192: Module object deallocation can free a live ThreadX kernel object
Eclipse Foundation · Eclipse ThreadX
Vendor fix available · Affected: Eclipse Foundation Eclipse ThreadX · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 4% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Eclipse Foundation · Eclipse ThreadXfrom 6.0.1 up to and including 6.5.1.202602a
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Eclipse Foundation
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-94192 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.