Module queue front-send validates a word count as a byte count

Summary

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.

Timeline

1. Oct 20, 2026, 2:35 PM UTCCVE published
2. Oct 20, 2026, 3:34 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Oct 20, 2026, 3:34 PM UTCRecord last updated
4. Oct 22, 2026, 9:34 PM UTCFirst seen by cve.now

Affected versions

• ThreadX

  From 6.0.1 · through 6.5.1.202602a

References 1