Medium Denial of service

CVE-2026-95108 — Deleting a user-mode module thread leaks its privileged kernel stack

One logical thread of a user-mode ThreadX module costs the Module Manager's shared object pool two allocations, not one. The module asks for a `TX_THREAD` control block through `txm_module_object_allocate`; `_txm_module_manager_thread_create` then takes a second allocation of `TXM_MODULE_KERNEL_STACK_SIZE` bytes for the privileged kernel stack that thread's system calls run on, and records it in the control block. Both come from `_txm_module_manager_object_pool` and both are linked onto the module's allocation list. The Module Manager's thread-delete dispatcher released only the first. The kernel stack stayed allocated until the whole module was stopped, so a module that creates, terminates and deletes threads in a loop — every state transition valid, every service returning `TX_SUCCESS` — removed a fixed block from a finite pool shared by the manager and by every other loaded module, on every cycle, for as long as it stayed loaded. Once the pool is exhausted, no memory-protected module can create any kernel object and no user-mode module thread can be created anywhere in the system. Vulnerable function: `_txm_module_manager_tx_thread_delete_dispatch`, in `common_modules/module_manager/inc/txm_module_manager_dispatch.h`.

Published Oct 20, 2026 · Updated Oct 20, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: eclipse

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Eclipse Foundation

Threadx

CVSS base

6.8

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Eclipse Foundation Threadx).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Eclipse Foundation	Threadx	≥ 6.0.1 and ≤ 6.5.1.202602a	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Attack requirements

None

Privileges required

Low

User interaction

None

Scope

Confidentiality (vulnerable system)

None

Integrity (vulnerable system)

None

Availability (vulnerable system)

High

Confidentiality (subsequent)

None

Integrity (subsequent)

None

Availability (subsequent)

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
6.8	CVSS 4.0	Medium	—	—	emo@eclipse.org via NIST National Vulnerability Database
6.8	CVSS 4.0	Medium	—	—	eclipse via CVE Program (cve.org) e CISA ADP

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

(score shown at the top: emo@eclipse.org)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-400 · Uncontrolled Resource Consumption

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Track CPU/memory spikes and availability drops correlated with request patterns.

endpoint telemetry (EDR)resource metrics

Timeline

What happened to this CVE, newest first.

2026
Source status changed · Received → Awaiting Analysis
Oct 20, 2026 · NIST National Vulnerability Database
SSVC assessment updated
Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
Affected products added · eclipse foundation/eclipse threadx
Oct 20, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 20, 2026
CVSS changed · 6.8
Oct 20, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 20, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 20, 2026 · Alertas do Telegram
CVE published
Oct 20, 2026 · eclipse

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 20, 2026 – Oct 20, 2026
1× Official description updated · Oct 20, 2026 – Oct 20, 2026

References

1 on the record

github.com/eclipse-threadx/threadx/security/advisories/GHSA-9hhf-6357-hpgq
NIST National Vulnerability Database

Elsewhere on this site

Eclipse Foundation
every CVE for this vendor

Denial of service
same class

CWE-400
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-94192 Module object deallocation can free a live ThreadX kernel object 1d
Medium CVE-2026-94202 Module block-pool create validates two of the four parameter words it reads 1d
High CVE-2026-95107 Module object allocation size overflow corrupts the manager object pool 1d
High CVE-2026-95109 Cortex-A7 module data validation checks only the first address of a caller-supplied range 1d
Medium CVE-2026-94023 Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion 1d
Medium CVE-2026-94024 Module Manager object lookup validates one byte of a module's search name 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-95108 is "Deleting a user-mode module thread leaks its privileged kernel stack", rated Medium. It affects Threadx (Eclipse Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.