CVE-2026-94192: CWE-416 Use After Free in Eclipse Foundation Eclipse ThreadX
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.
CVSS v4.0
Score 8.5high
Affected software
Eclipse Foundation
Eclipse ThreadX
pkg:github/eclipse-threadx/threadxRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Eclipse ThreadX contains a use-after-free vulnerability (CWE-416) in its module management system. The ThreadX module allocates kernel object control blocks from the Module Manager's object pool and can request deallocation via txm_module_object_deallocate. However, the deallocation process only releases the memory but does not remove the object from the created list or scheduling lists. Consequently, kernel objects such as threads and timers remain active and schedulable, while their underlying memory may be reallocated for other uses, leading to use-after-free conditions and potential system instability or compromise.
Potential Impact
This vulnerability can lead to memory corruption and unpredictable behavior in the affected system. Since kernel objects remain active after their memory is freed, attackers or faulty modules could exploit this to cause crashes, data corruption, or potentially escalate privileges within the system. The CVSS 4.0 score of 8.5 reflects a high impact with local attack vector and low complexity, requiring low privileges but no user interaction.
Mitigation Recommendations
No explicit patch or remediation is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider restricting access to the affected ThreadX module and monitor for updates from the Eclipse Foundation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- eclipse
- Date Reserved
- 2026-09-23T13:42:24.290Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ad789f82cdf04f6563b84a9
Added to database: 10/20/2026, 15:34:16 UTC
Last enriched: 10/20/2026, 15:48:21 UTC
Last updated: 10/20/2026, 19:06:08 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.