# 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.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-xj75-fc68-h4rw

## 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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-253 (Incorrect Check of Function Return Value)

## Which versions are affected by CVE-2026-0648?

It affects 1 product.


Products: 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.

## 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](https://insights.sbomify.com/CVE-2024-2212/): Integer overflow in ThreadX (high 7.3)
- [CVE-2025-55080](https://insights.sbomify.com/CVE-2025-55080/): Improper Parameter Check in ThreadX Syscall Implementation (high 7.2)
- [CVE-2024-2214](https://insights.sbomify.com/CVE-2024-2214/): Missing array size check in _Mtxinit() in the Xtensa port (high 7.0)
- [CVE-2025-55079](https://insights.sbomify.com/CVE-2025-55079/): Missing check for thread priority (medium 5.7)
- [CVE-2025-55078](https://insights.sbomify.com/CVE-2025-55078/): Incomplete validation of kernel object pointers in system calls (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0648 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-0648 in the wild and no public exploit code.

Affected product: Eclipse ThreadX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0648/ (Markdown: https://insights.sbomify.com/CVE-2026-0648/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0648
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0648
- OSV: https://osv.dev/vulnerability/CVE-2026-0648

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0648/
Summaries are generated and may contain mistakes; the official description above is the record.