Eclipse ThreadX module deallocation frees live kernel objects
Key facts
- Attack vector
- Local
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-416 and the CVSS impact.
Summary
Eclipse ThreadX from 6.0.1 through 6.5.1.202602a is affected. The module object deallocation function releases memory that still holds a kernel object control block the kernel is using (CWE-416). A local user with low privileges can affect confidentiality, integrity and availability, because the freed bytes can be reallocated to another use.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Eclipse Foundation | Eclipse ThreadX | 6.0.1 – 6.5.1.202602a | 6.5.2.202603 | Patch available | CNA |
- Eclipse ThreadX VendorEclipse Foundation Affected 6.0.1 – 6.5.1.202602a Fixed in 6.5.2.202603 Patch available CNA
Remediation
Upgrade Eclipse ThreadX to 6.5.2.202603, which fixes this flaw. The sources list no advisory identifier for the fix.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA Eclipse ThreadX (Eclipse Foundation) Fixed in 6.5.2.202603
Timeline
- 2026-10-20 Threatist record created from CVE-2026-94192
- 2026-10-20 CISA SSVC decision points changed
- 2026-10-20 Priority changed: MEDIUM → LOW
More Eclipse Foundation vulnerabilities
- TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
- TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
- TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
- TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
- TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
- TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences