Medium severity · published Oct 20, 2026
CVE-2026-95111
Module queue front-send validates a word count as a byte count
4.8
CVSS
0.1%
EPSS
No
On KEV
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 3% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
ET
Eclipse ThreadX · Eclipse Foundation
6.0.1 through 6.5.1.202602a · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-95111
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-95111
github.com
https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-rrg6-24r9-wqpm
More from Eclipse ThreadX
8.5
CVE-2026-95109
Cortex-A7 module data validation checks only the first address of a caller-supplied range
8.5
CVE-2026-94192
Module object deallocation can free a live ThreadX kernel object
7.0
CVE-2026-95107
Module object allocation size overflow corrupts the manager object pool
6.9
CVE-2026-94024
Module Manager object lookup validates one byte of a module's search name
6.9
CVE-2026-94023
Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion
