ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-95108

One logical thread of a user-mode ThreadX module costs the Module Manager's shared object pool two allocations, not one.

Published Oct 20, 2026 · catalog updated Oct 20, 2026 · One logical thread of

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-95108. EPSS is 0.17%. Act only if a listed version of One logical thread of is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (One logical thread of).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium6.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.17%
Remediation
Advisory link
Affected products
See sources for product scope

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 control block through ; then takes a second allocation of bytes for the privileged kernel stack that thread's system calls run on, and records it in the control block. Both come from 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 — 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: , in .

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2026-95108

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the cve_org record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-95108. EPSS is 0.17%. Act only if a listed version of One logical thread of is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption; CWE-772: Missing Release of Resource after Effective Lifetime. EPSS 0.17%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 20, 2026 · NIST NVD

    Detected

    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 control block through ; then takes a second allocation of bytes for the privileged kernel stack that thread's system calls run on, and records it in the control block. Both come from and both are linked onto the module's allocation list. The Module Manager'

  2. Oct 20, 2026 · NIST NVD

    Updated

    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 control block through ; then takes a second allocation of bytes for the privileged kernel stack that thread's system calls run on, and records it in the control block. Both come from and both are linked onto the module's allocation list. The Module Manager'

  3. Oct 20, 2026 · NIST NVD

    Updated

    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 control block through ; then takes a second allocation of bytes for the privileged kernel stack that thread's system calls run on, and records it in the control block. Both come from and both are linked onto the module's allocation list. The Module Manager'

Sources

  • CVE.orgVulnerability recordCVE-2026-95108

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-95108

    30-day exploitation probability 0.17%

    first.org
  • NIST NVDVulnerability recordCVE-2026-95108

    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 control block through ; then takes a second allocation of `TX

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 23, 2026
  • CVE.orgOct 21, 2026
  • NIST NVDOct 21, 2026