CVE-2026-97509

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

thunderbolt: Keep XDomain reference during the lifetime of a service

This is needed because we release the service ID in tb_service_release() and the ID array is owned by the parent XDomain.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

October 3, 2026

Advisory Details (5)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

thunderbolt: Keep XDomain reference during the lifetime of a service - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea60ae6233ca0fc0d414e9c11f0d86c63b303fc7
generic

thunderbolt: Keep XDomain reference during the lifetime of a service - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/daeaa6c7211d03ed061b0dd22a875fad9372b090
generic

thunderbolt: Keep XDomain reference during the lifetime of a service - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a4567e5380e4e46d0ea9a28d2d675e5c6f013d54
generic

thunderbolt: Keep XDomain reference during the lifetime of a service - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b4060998637f06975fceee9b73845d8672d411e
generic

thunderbolt: Keep XDomain reference during the lifetime of a service - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8ab12d015884b8aa85ea7ed58c5a0bae4264fe60

Vendor Advisories for CVE-2026-97509(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 47× in last 7d / 69× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 06:57 UTCEG score recompute
  2. 2026-10-05 06:57 UTCVendor advisory
  3. 2026-10-05 06:57 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 20:06 UTCVendor advisory
  6. 2026-10-04 20:06 UTCGHSA enrichment
  7. 2026-10-04 09:14 UTCVendor advisory
  8. 2026-10-04 09:14 UTCGHSA enrichment
  9. 2026-10-03 22:23 UTCEG score recompute
  10. 2026-10-03 22:23 UTCVendor advisory
  11. 2026-10-03 22:23 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 11:30 UTCVendor advisory
  14. 2026-10-03 11:30 UTCGHSA enrichment
  15. 2026-10-03 06:37 UTCVendor advisory
  16. 2026-10-03 06:37 UTCGHSA enrichment
  17. 2026-10-02 19:46 UTCEG score recompute
  18. 2026-10-02 19:46 UTCVendor advisory
  19. 2026-10-02 19:46 UTCGHSA enrichment
  20. 2026-10-02 17:57 UTCEPSS rescore
  21. 2026-10-02 08:55 UTCVendor advisory
  22. 2026-10-02 08:54 UTCGHSA enrichment
  23. 2026-10-01 22:03 UTCEG score recompute
  24. 2026-10-01 22:03 UTCVendor advisory
  25. 2026-10-01 22:03 UTCGHSA enrichment
Show 44 more
  1. 2026-10-01 19:51 UTCEPSS rescore
  2. 2026-10-01 11:08 UTCVendor advisory
  3. 2026-10-01 11:08 UTCGHSA enrichment
  4. 2026-10-01 00:16 UTCEG score recompute
  5. 2026-10-01 00:16 UTCVendor advisory
  6. 2026-10-01 00:16 UTCGHSA enrichment
  7. 2026-09-30 15:04 UTCEPSS rescore
  8. 2026-09-30 12:43 UTCVendor advisory
  9. 2026-09-30 12:42 UTCGHSA enrichment
  10. 2026-09-30 01:50 UTCEG score recompute
  11. 2026-09-30 01:50 UTCVendor advisory
  12. 2026-09-30 01:50 UTCGHSA enrichment
  13. 2026-09-29 14:59 UTCVendor advisory
  14. 2026-09-29 14:59 UTCGHSA enrichment
  15. 2026-09-29 04:09 UTCEG score recompute
  16. 2026-09-29 04:09 UTCVendor advisory
  17. 2026-09-29 04:09 UTCGHSA enrichment
  18. 2026-09-28 17:18 UTCEG score recompute
  19. 2026-09-28 17:18 UTCVendor advisory
  20. 2026-09-28 17:17 UTCGHSA enrichment
  21. 2026-09-28 13:52 UTCEPSS rescore
  22. 2026-09-28 13:52 UTCEPSS rescore
  23. 2026-09-28 06:24 UTCEG score recompute
  24. 2026-09-28 06:24 UTCGHSA enrichment
  25. 2026-09-28 05:47 UTCEG score recompute
  26. 2026-09-28 05:47 UTCGHSA enrichment
  27. 2026-09-27 22:34 UTCEG score recompute
  28. 2026-09-27 22:34 UTCGHSA enrichment
  29. 2026-09-27 13:49 UTCEPSS rescore
  30. 2026-09-27 11:43 UTCGHSA enrichment
  31. 2026-09-27 00:48 UTCEG score recompute
  32. 2026-09-27 00:48 UTCGHSA enrichment
  33. 2026-09-26 15:59 UTCEPSS rescore
  34. 2026-09-26 13:57 UTCGHSA enrichment
  35. 2026-09-26 03:02 UTCEG score recompute
  36. 2026-09-26 03:02 UTCGHSA enrichment
  37. 2026-09-25 16:09 UTCEG score recompute
  38. 2026-09-25 16:09 UTCGHSA enrichment
  39. 2026-09-25 05:17 UTCEG score recompute▲ 8.80
  40. 2026-09-25 05:17 UTCGHSA enrichment
  41. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  42. 2026-09-24 17:33 UTCNVD update
  43. 2026-09-24 16:27 UTCEG score recompute
  44. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97509?
CVE-2026-97509 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Keep XDomain reference during the lifetime of a service This is needed because we release the service ID in tbservicerelease() and the ID array is owned by the parent XDomain.
When was CVE-2026-97509 disclosed?
CVE-2026-97509 was first published on September 24, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97509 actively exploited?
CVE-2026-97509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97509?
CVE-2026-97509 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97509?
No fix for CVE-2026-97509 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97509 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-97509

Explore →

Is Your Infrastructure Affected by CVE-2026-97509?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs