CVE-2026-95111
Awaiting Analysis Awaiting Analysis - Queue

Memory Corruption in ThreadX RTOS Queue Handling

Vulnerability report for CVE-2026-95111, 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 memory-protected ThreadX module's queue request reaches the Module Manager's dispatch layer, which decides how much of the module's buffer the privileged queue copy may touch and hands that extent to the module port's range check. A queue's `tx_queue_message_size` is a count of `ULONG`s and the copy moves that many words, so the extent is `message_size * sizeof(ULONG)` bytes. The front-send dispatcher passed the word count itself. `tx_queue_send` and `tx_queue_receive`, either side of it in the same header, have always multiplied. A source buffer ending `message_size` bytes into memory the module may read was therefore accepted, and `_txe_queue_front_send` then read `message_size * sizeof(ULONG)` bytes from it in privileged mode β€” `3 * message_size` bytes past the end of what the module is allowed to read. The words are written into the queue's message area, so a module that can receive from that queue reads them back.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-20
Generated
2026-11-09
AI Q&A
2026-10-20
EPSS Evaluated
2026-11-08
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-131 The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves a memory-protected ThreadX module's queue request reaching the Module Manager's dispatch layer. The issue occurs because the front-send dispatcher incorrectly passes the word count instead of the byte count for the buffer size. This causes the system to read up to three times the allowed message size from memory the module is permitted to access, potentially exposing adjacent memory regions.

Detection Guidance

This vulnerability is specific to Eclipse ThreadX versions 6.0.1 to 6.5.1.202602a. Detection involves checking the ThreadX version in use. Commands like `grep -r "TX_QUEUE_MESSAGE_MAX_SIZE" /path/to/threadx` or inspecting version headers in the codebase can help identify affected versions.

Impact Analysis

The vulnerability allows a memory-protected module to read up to 48 or 96 bytes of memory beyond its permitted access. This could lead to unauthorized data disclosure if adjacent memory contains sensitive information. The impact is limited as the module cannot choose the memory location and the read window is bounded.

Compliance Impact

This vulnerability may lead to unauthorized memory access, which could result in data leakage or corruption. For GDPR, this could violate principles of data protection and integrity. For HIPAA, it might compromise protected health information confidentiality. However, the impact is limited due to the bounded read window and lack of module control over the read address.

Mitigation Strategies

Upgrade to ThreadX version 6.5.2.202603 or later, which includes the fix for this issue. If upgrading is not immediately possible, disable the `tx_queue_front_send` service in affected modules by defining `TXM_QUEUE_FRONT_SEND_CALL_NOT_USED`.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-95111. 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...