ThreadX Modules invokes trace-full callbacks after module unload
Affects ThreadX 6.0.1 through 6.5.2.202603 with ThreadX Modules when event tracing is enabled. Fixed in 6.5.2.202603b.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.5.2.202603b
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. ThreadX versions 6.0.1 through 6.5.2.202603 with ThreadX Modules Event tracing enabled (TX_ENABLE_EVENT_TRACE) Trace-buffer-full notification exposed to modules A kernel-owned trace buffer remains active after the module is unloaded Module code is dynamically allocated
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.3/10CVSS 7.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
CVE-2026-113421 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.3 (high) and affects Eclipse ThreadX; fixed in 6.5.2.202603b.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.11% · 1st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.5.2.202603b
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Eclipse ThreadX, a real-time operating system kernel, is affected when its Modules feature is used with event tracing enabled. After a module is stopped and unloaded, a trace-buffer-full callback it registered can still run, potentially with kernel privileges, allowing attackers to execute code, redirect control flow, or crash the system.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
ThreadX versions 6.0.1 through 6.5.2.202603 with ThreadX Modules Event tracing enabled (TX_ENABLE_EVENT_TRACE) Trace-buffer-full notification exposed to modules A kernel-owned trace buffer remains active after the module is unloaded Module code is dynamically allocatedUpgrade to a fixed version: 6.5.2.202603b.
Workaround: Build without TX_ENABLE_EVENT_TRACE, or do not enable tracing at run time, on systems that load untrusted modules. Alternatively, define TXM_TRACE_BUFFER_FULL_NOTIFY_CALL_NOT_USED when building the Module Manager.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Eclipse Foundation Eclipse ThreadX
From 6.0.1 · through 6.5.2.202603
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113421
Is CVE-2026-113421 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A trace-buffer-full callback that a module registered can still run after the module is unloaded. The callback's code runs in privileged context, which bypasses the module's lifetime and isolation boundaries. If the released memory is reused or inaccessible, this can redirect control flow or cause a fault.Source: github.com
Which versions are affected by CVE-2026-113421?
Eclipse ThreadX: from 6.0.1 through 6.5.2.202603.Source: cve.now feed data
Am I affected, and how do I check?
The issue affects ThreadX versions 6.0.1 through 6.5.2.202603 when TX_ENABLE_EVENT_TRACE is enabled, the trace-buffer-full notification is exposed to modules, and module code is dynamically allocated. To check a build, look at the ThreadX version and whether TX_ENABLE_EVENT_TRACE is defined in its configuration.Source: github.com
How do I fix CVE-2026-113421?
Upgrade to ThreadX 6.5.2.202603b, which contains the fix.Source: github.com