CVE-2026-93817

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.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:

perf: Fix addr_filter_ranges lifetime

Lee Jia Jie reported that since event::addr_filter_ranges is used under RCU, it should be RCU freed.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/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
Severity78% × 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.1%
EPSS %ILE
2nd
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

September 25, 2026

Advisory Details (3)

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

perf: Fix addr_filter_ranges lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf: Fix addr_filter_ranges lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

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

perf: Fix addr_filter_ranges lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f1853b2b9f38f1343790bae8c0601b3f7554754

Vendor Advisories for CVE-2026-93817(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 41× in last 7d / 63× 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 04:44 UTCEG score recompute
  2. 2026-10-05 04:44 UTCVendor advisory
  3. 2026-10-05 04:44 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 17:46 UTCVendor advisory
  6. 2026-10-04 17:46 UTCGHSA enrichment
  7. 2026-10-04 06:48 UTCVendor advisory
  8. 2026-10-04 06:48 UTCGHSA enrichment
  9. 2026-10-03 19:51 UTCEG score recompute
  10. 2026-10-03 19:51 UTCVendor advisory
  11. 2026-10-03 19:51 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 08:54 UTCVendor advisory
  14. 2026-10-03 08:54 UTCGHSA enrichment
  15. 2026-10-02 21:57 UTCEG score recompute
  16. 2026-10-02 21:57 UTCVendor advisory
  17. 2026-10-02 21:57 UTCGHSA enrichment
  18. 2026-10-02 11:00 UTCVendor advisory
  19. 2026-10-02 11:00 UTCGHSA enrichment
  20. 2026-10-02 00:03 UTCEG score recompute
  21. 2026-10-02 00:03 UTCVendor advisory
  22. 2026-10-02 00:03 UTCGHSA enrichment
  23. 2026-10-01 19:51 UTCEPSS rescore
  24. 2026-10-01 12:30 UTCVendor advisory
  25. 2026-10-01 12:30 UTCGHSA enrichment
Show 38 more
  1. 2026-10-01 01:33 UTCEG score recompute
  2. 2026-10-01 01:33 UTCVendor advisory
  3. 2026-10-01 01:33 UTCGHSA enrichment
  4. 2026-09-30 15:04 UTCEPSS rescore
  5. 2026-09-30 14:37 UTCVendor advisory
  6. 2026-09-30 14:37 UTCGHSA enrichment
  7. 2026-09-30 03:20 UTCVendor advisory
  8. 2026-09-30 03:20 UTCGHSA enrichment
  9. 2026-09-29 16:24 UTCEG score recompute
  10. 2026-09-29 16:24 UTCVendor advisory
  11. 2026-09-29 16:23 UTCGHSA enrichment
  12. 2026-09-29 05:24 UTCEG score recompute
  13. 2026-09-29 05:24 UTCVendor advisory
  14. 2026-09-29 05:24 UTCGHSA enrichment
  15. 2026-09-28 18:28 UTCVendor advisory
  16. 2026-09-28 18:28 UTCGHSA enrichment
  17. 2026-09-28 07:31 UTCVendor advisory
  18. 2026-09-28 07:31 UTCGHSA enrichment
  19. 2026-09-27 20:34 UTCEG score recompute
  20. 2026-09-27 20:34 UTCGHSA enrichment
  21. 2026-09-27 13:49 UTCEPSS rescore
  22. 2026-09-27 09:36 UTCGHSA enrichment
  23. 2026-09-26 22:40 UTCEG score recompute
  24. 2026-09-26 22:39 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
  26. 2026-09-26 11:40 UTCGHSA enrichment
  27. 2026-09-26 00:44 UTCEG score recompute
  28. 2026-09-26 00:43 UTCGHSA enrichment
  29. 2026-09-25 13:23 UTCEG score recompute
  30. 2026-09-25 13:22 UTCGHSA enrichment
  31. 2026-09-25 12:56 UTCEG score recompute
  32. 2026-09-25 12:56 UTCGHSA enrichment
  33. 2026-09-25 05:17 UTCEG score recompute▲ 7.80
  34. 2026-09-25 05:17 UTCGHSA enrichment
  35. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  36. 2026-09-24 17:33 UTCNVD update
  37. 2026-09-24 16:30 UTCEG score recompute
  38. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93817?
CVE-2026-93817 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: perf: Fix addrfilterranges lifetime Lee Jia Jie reported that since event::addrfilterranges is used under RCU, it should be RCU freed.
When was CVE-2026-93817 disclosed?
CVE-2026-93817 was first published on September 24, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93817 actively exploited?
CVE-2026-93817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93817?
CVE-2026-93817 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93817?
No fix for CVE-2026-93817 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-93817 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-93817

Explore →

Is Your Infrastructure Affected by CVE-2026-93817?

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

Book a Demo →Browse All CVEs