CVE-2026-94023
Received Received - Intake

ThreadX Kernel Object Deletion Vulnerability in Module Manager

Vulnerability report for CVE-2026-94023, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-20

Last updated on: 2026-10-20

Assigner: Eclipse Foundation

Description

A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended β€” `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex. Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-20
Generated
2026-10-20
AI Q&A
2026-10-20
EPSS Evaluated
N/A
NVD
EUVD

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-125 The product reads data past the end, or before the beginning, of the intended buffer.
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Eclipse ThreadX allows a low-privilege module to delete kernel objects owned by other modules or the application through the privileged Module Manager dispatcher. The flaw occurs because ownership checks happen after deletion begins and memory dereferencing lacks bounds checking, leading to potential system faults or memory corruption.

Detection Guidance

Detecting this vulnerability requires checking ThreadX versions between 6.0.1 and 6.5.1.202602a. Use commands like 'tx_kernel_version_get()' in your application or inspect version strings in ThreadX binaries. Look for unexpected kernel object deletions or synchronization failures in logs.

Impact Analysis

Exploitation can break synchronization between components, causing waiters to wake unexpectedly, timers to stop, memory pools to disappear, and mutex priorities to change. These effects are unrecoverable as objects are deleted before checks can refuse the request, potentially crashing the system or corrupting data.

Mitigation Strategies

Upgrade ThreadX to version 6.5.2.202603 or later. If upgrading is not possible, avoid loading untrusted modules or restrict module interactions to prevent unauthorized object deletions.

Chat Assistant

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

EPSS Chart