CVE-2026-113421
Received Received - Intake

Eclipse ThreadX Privilege Escalation via Trace Buffer Callback

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: Eclipse Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-03
Last Modified
2026-11-03
Generated
2026-11-03
AI Q&A
2026-11-03
EPSS Evaluated
N/A
NVD
CVE-2026-113421
EUVD
EUVD-2026-115717

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Eclipse Foundation Eclipse ThreadX 6.0.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-416 The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in Eclipse ThreadX versions 6.0.1 through 6.5.2.202603. When a module is unloaded, its trace-buffer-full callback is not revoked. If event tracing is enabled and a kernel-owned trace buffer is active, a buffer wrap can trigger the callback from a privileged thread context after the module's code has been released. This allows a user-mode module to execute code with kernel privileges after unloading, bypassing isolation boundaries.

Detection Guidance

Detecting this vulnerability requires checking for ThreadX versions 6.0.1 through 6.5.2.202603 and verifying if event tracing is enabled. Inspect module unloading behavior and trace-buffer-full callback registrations. No direct commands are provided in the resources, but monitoring for unexpected privileged code execution post-module unload may indicate exploitation.

Impact Analysis

An attacker with local access and low privileges could exploit this to execute arbitrary code in kernel context. This could lead to system compromise, data theft, or denial of service. The impact includes high confidentiality, integrity, and availability risks due to kernel-level code execution.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. System integrity breaches may also occur, potentially compromising audit trails and data integrity controls required by these regulations.

Mitigation Strategies

Immediately upgrade to ThreadX version 6.5.2.202603b or later to patch the vulnerability. As a workaround, disable event tracing or remove the trace notification service from the Module Manager to prevent trace-buffer-full callbacks from being invoked.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-113421. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...