{
  "affected": [
    {
      "ranges": [
        {
          "database_specific": {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "6.0.1"
                  },
                  {
                    "last_affected": "6.5.1.202602a"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              }
            ]
          },
          "events": [
            {
              "introduced": "6a018a4cfda937c0d8cbdee761187c5c5843e115"
            },
            {
              "last_affected": "b91b03b9e75fa523b17127f9e0eca09dca916459"
            }
          ],
          "repo": "https://github.com/eclipse-threadx/threadx",
          "type": "GIT"
        }
      ]
    }
  ],
  "aliases": [
    "GHSA-9hhf-6357-hpgq"
  ],
  "database_specific": {
    "cna_assigner": "eclipse",
    "cwe_ids": [
      "CWE-400",
      "CWE-772"
    ],
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/95xxx/CVE-2026-95108.json"
  },
  "details": "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.\n\n\n\nThe 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.\n\n\n\nVulnerable function: `_txm_module_manager_tx_thread_delete_dispatch`, in `common_modules/module_manager/inc/txm_module_manager_dispatch.h`.",
  "id": "CVE-2026-95108",
  "modified": "2026-10-21T02:30:39.821892682Z",
  "published": "2026-10-20T15:19:16.940Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/95xxx/CVE-2026-95108.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-9hhf-6357-hpgq"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-95108"
    }
  ],
  "schema_version": "1.9.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Deleting a user-mode module thread leaks its privileged kernel stack"
}