Eclipse Foundation Eclipse ThreadX
ThreadX Modules invokes trace-full callbacks after module unload
In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, ThreadX Modules does not revoke a module's trace-buffer-full callback when the module is stopped and unloaded. With event tracing enabled and a kernel-owned trace buffer still active, a later buffer wrap invokes the callback from privileged thread context after the module's code has been released, so a user-mode module can have its code run with kernel privileges after unload, or, once the memory is reused, redirect control flow or cause a fault.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.3high · scored by CNA · CWE-416
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.2.202603
Mitigation
The record names no fix. Check the vendor advisory below.
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.