CVE-2026-0648 Memory corruption in Eclipse ThreadX
Incorrect error handling in Eclipse ThreadX OSEK layer causes wild pointer writes, leading to memory corruption and denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-0648?
CVE-2026-0648 is a high-severity memory corruption vulnerability in Eclipse ThreadX, published on 27 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
The vulnerability stems from an incorrect error-checking logic in the CreateCounter() function (in threadx/utility/rtos_compatibility_layers/OSEK/tx_osek.c) when handling the return value of osek_get_counter(). Specifically, the current code checks if cntr_id equals 0u to determine failure, but @osek_get_counter() actually returns E_OS_SYS_STACK (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 (OSEK_COUNTER *), 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.
Which versions are affected by CVE-2026-0648?
It affects 1 product.
Products include Eclipse Threadx.
How do I fix CVE-2026-0648?
No fix has been published for CVE-2026-0648 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-0648 being exploited?
There is no known exploitation of CVE-2026-0648 in the wild and no public exploit code.
Other vulnerabilities in Eclipse ThreadX
- CVE-2024-2212 Integer overflow in ThreadX
- CVE-2025-55080 Improper Parameter Check in ThreadX Syscall Implementation
- CVE-2024-2214 Missing array size check in _Mtxinit() in the Xtensa port
- CVE-2025-55079 Missing check for thread priority
- CVE-2025-55078 Incomplete validation of kernel object pointers in system calls
Sources
Also known as GHSA-xj75-fc68-h4rw.