Eclipse Foundation Eclipse ThreadX
Module object allocation size overflow corrupts the manager object pool
A ThreadX module chooses `object_size` when it calls `txm_module_object_allocate`. The Module Manager adds its own 16-byte private header to that size and asked the object pool for the result **without checking the addition**. A size near the top of a `ULONG` wrapped, the pool served a block far smaller than the header, and the manager then wrote the header past the end of it and into the neighbouring byte-pool block.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.0high · scored by CNA · CWE-190
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Eclipse Foundation Eclipse ThreadX
- >= 6.0.1, <= 6.5.1.202602a
Fixed in 6.5.2.202603
Mitigation
Upgrade Eclipse ThreadX to 6.5.2.202603 or later.
References
- Vendor advisory github.com/eclipse-threadx/threadx/security/ad…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.