Eclipse ThreadX 6.0.1-6.5.2.202603 PrivEsc via Unrevoked TraceBufferFull Callback
CVE-2026-113421 Published on November 3, 2026
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.
Vulnerability Analysis
CVE-2026-113421 can be exploited with local system access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity and availability.
Weakness Type
What is a Dangling pointer Vulnerability?
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.
CVE-2026-113421 has been classified to as a Dangling pointer vulnerability or weakness.
Products Associated with CVE-2026-113421
Want to know whenever a new CVE is published for Eclipse Threadx? stack.watch will email you.
Affected Versions
Eclipse Foundation Eclipse ThreadX:- Version 6.0.1, <= 6.5.2.202603 is affected.