NetSight
high7.3

CVE-2026-113421

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 un…

Impact

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.

An attacker can exploit this with local access to the system, with a regular user account, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of data being read, high risk of data or systems being changed, high risk of outages.

Affected products · Eclipse Foundation

ProductAffected versions
Eclipse ThreadX
from 6.0.1 through 6.5.2.202603
Version 6.0.1 ≤6.5.2.202603

Weakness classification

References