Live › vulnerability › CVE-2026-95111
Go to dashboardIn memory-protected ThreadX modules, the front-send queue dispatcher passes a word count where a byte count is needed, so the range check accepts a source buffer too short for the copy. The privileged copy then reads several times the allowed length from memory outside the module's range, and the words land in the queue where the module can read them back.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Embedded systems that run ThreadX with the memory-protected Module Manager and let a module send to queues with _txe_queue_front_send. Systems using ThreadX without the Module Manager, or without memory-protected modules, are not in the described code path. The sources do not name affected ThreadX versions or a patched release.
No product ranges from the sources yet.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 ULONGs 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.
This page as .md · .json · in your agent: get_signal("CVE-2026-95111")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.