Module object allocation size overflow corrupts the manager object pool

{
  "id": "a9a7cd41dc444ba37811c05b812339dd78758f7a2c164595529eceaeca637dae",
  "url": "https://osv.dev/vulnerability/CVE-2026-95107",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Module object allocation size overflow corrupts the manager object pool",
    "summary": "A ThreadX module chooses `object_size` when it calls `txm_module_object_allocate`. The Module Manager adds its own 16-byte private header to that size and asked the object pool for the result **without checking the addition**. A size near the top of a `ULONG` wrapped, the pool served a block far smaller than the header, and the manager then wrote the header past the end of it and into the neighbouring byte-pool block.",
    "evidence": "osv:CVE-2026-95107",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-95107",
      "aliases": [
        "CVE-2026-95107",
        "GHSA-63qc-jcr6-qw6r"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "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"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/eclipse-threadx/threadx",
              "type": "GIT",
              "events": [
                {
                  "introduced": "6a018a4cfda937c0d8cbdee761187c5c5843e115"
                },
                {
                  "last_affected": "b91b03b9e75fa523b17127f9e0eca09dca916459"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "6.0.1"
                      },
                      {
                        "last_affected": "6.5.1.202602a"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StandardRange"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v6.4.1_rel",
            "v6.5.1.202602a_rel",
            "v6.5.1.202602_rel",
            "v6.5.0.202601_rel",
            "v6.4.5.202504_rel",
            "v6.4.3.202503_rel",
            "v6.4.2_rel",
            "v6.4.0_rel",
            "v6.3.0_rel",
            "v6.2.1_rel",
            "v6.2.0_rel",
            "v6.1.12_rel",
            "v6.1.11_rel",
            "v6.1.10_rel",
            "v6.1.9_rel",
            "v6.1.8_rel",
            "v6.1.7_rel",
            "v6.1.6_rel",
            "v6.1.5_rel",
            "v6.1.3_rel",
            "v6.1.2_rel",
            "v6.1.1_rel",
            "v6.1_rel",
            "v6.0.2_rel",
            "v6.0.1_rel"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-95107.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.771239770Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/95xxx/CVE-2026-95107.json",
        "https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-63qc-jcr6-qw6r",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-95107"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-190",
          "CWE-680",
          "CWE-787"
        ],
        "cna_assigner": "eclipse",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/95xxx/CVE-2026-95107.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-95107",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 493501,
  "published_at": "2026-10-20T15:20:15.011+00:00"
}