{
  "id": "CVE-2026-113421",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-113421",
  "published_at": "2026-11-03T08:27:59.776Z",
  "title": "ThreadX Modules invokes trace-full callbacks after module unload",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse ThreadX",
  "cvss": {
    "score": 7.3,
    "source": "cna",
    "vector": "CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, ThreadX Modules does not revoke a module's trace-buffer-full callback when the module is stopped and unloaded. With event tracing enabled and a kernel-owned trace buffer still active, a later buffer wrap invokes the callback from privileged thread context after the module's code has been released, so a user-mode module can have its code run with kernel privileges after unload, or, once the memory is reused, redirect control flow or cause a fault.",
  "cwe": "CWE-416",
  "cvss_by_source": {
    "cna": 7.3
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Eclipse Foundation",
        "product": "Eclipse ThreadX",
        "ranges": [
          "\u003e= 6.0.1, \u003c= 6.5.2.202603"
        ],
        "fixed_in": null
      }
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-8pgj-qvjv-j4fq"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
