In Eclipse ThreadX before version 6.4.0, the Mtxinit() function in the Xtensa port was missing an array size check causing a memory overwrite. The affected file was ports/xtensa/xcc/src/txcliblock.c

In Eclipse ThreadX before 6.4.0, xQueueCreate() and xQueueCreateSet() functions from the FreeRTOS compatibility API (utility/rtoscompatibilitylayers/FreeRTOS/txfreertos.c) were missing parameter checks. This could lead to integer wraparound, under-allocations and heap buffer overflows.

The vulnerability stems from an incorrect error-checking logic in the CreateCounter() function (in threadx/utility/rtoscompatibilitylayers/OSEK/txosek.c) when handling the return value of osekgetcounter(). Specifically, the current code checks if cntrid equals 0u to determine failure, but @osekgetcounter() actually returns EOSSYSSTACK (defined as 12U) when it fails. This mismatch causes the error branch to never execute even when the counter pool is exhausted.

As a result, when the counter pool is depleted, the code proceeds to cast the error code (12U) to a pointer (OSEKCOUNTER ), creating a wild pointer. Subsequent writes to members of this pointer lead to writes to illegal memory addresses (e.g., 0x0000000C), which can trigger immediate HardFaults or silent memory corruption.

This vulnerability poses significant risks, including potential denial-of-service attacks (via repeated calls to exhaust the counter pool) and unauthorized memory access.