CVE-2026-115653

Cortex-M module ports save a preempted user-mode module thread's registers through its unchecked stack pointer in privileged mode

Published Nov 2, 2026 CVSS 4.0 · 7 High EPSS < 1% KEV · Not listed
Description
In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the PendSV handler of the Cortex-M module ports saves a preempted user-mode module thread's registers in privileged mode at addresses taken from the thread's stack pointer, without checking that pointer against the thread's stack. A user-mode, memory-protected module can thereby write up to nine words, eight of its choosing, or 25 with floating-point state, into memory immediately below any region it may write, and read back what is stored there.

Analysis

AI-generated

Technical impact

A stack pointer overflow in the PendSV handler of Cortex‑M module ports allows a pre‑empted user‑mode module to overwrite up to nine 32‑bit words, or twenty‑five when floating‑point state is present, on memory located immediately below the module’s own stack. This unchecked write can corrupt control structures or other adjacent data, which may compromise correctness or lead to control‑flow hijacking. The nature of the vulnerability matches a buffer‑overflow weakness, as the kernel writes beyond the bounds specified by the user module’s stack pointer.

Affected Systems

Eclipse ThreadX versions 6.0.1 through 6.5.2.202603 running on Cortex‑M devices are affected. Any system that hosts user‑mode, memory‑protected modules that can be pre‑empted by the kernel is therefore at risk. The product is maintained by the Eclipse Foundation.

Risk and Exploitability

The CVSS score of 7.0 places this issue in the high‑severity range. No EPSS score is provided, and the vulnerability is not listed in CISA’s KEV catalog, indicating no publicly known exploitation. The attack requires local access; an attacker must be able to run or influence a user‑mode module that the kernel will pre‑empt. If successful, the memory corruption could enable overwriting of core data structures and potentially allow privilege escalation or denial of service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Eclipse ThreadX to a patched release that validates stack pointers during PendSV handling (for example, version 6.5.3 or later).
  • Recompile the ThreadX kernel with the latest patch commit that includes stack‑pointer validation and rebuild the system image.
  • If an upgrade or recompilation is not immediately possible, restrict or disable preemption of user‑mode modules and enforce strict stack bounds via memory protection settings to reduce the risk of out‑of‑bounds writes.

Generated by OpenCVE AI on November 2, 2026 at 17:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Eclipse
Eclipse threadx
Vendors & Products Eclipse
Eclipse threadx
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the PendSV handler of the Cortex-M module ports saves a preempted user-mode module thread's registers in privileged mode at addresses taken from the thread's stack pointer, without checking that pointer against the thread's stack. A user-mode, memory-protected module can thereby write up to nine words, eight of its choosing, or 25 with floating-point state, into memory immediately below any region it may write, and read back what is stored there.
Title Cortex-M module ports save a preempted user-mode module thread's registers through its unchecked stack pointer in privileged mode
Weaknesses CWE-787
CWE-822
References
Metrics cvssV4_0

{'score': 7, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Nov 2, 2026, 4:17 PM
Reserved
Oct 23, 2026, 7:04 AM
Status
Awaiting Analysis
Published
Nov 2, 2026, 4:17 PM
Modified
Nov 2, 2026, 7:14 PM