CVE-2026-97513

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:

media: chips-media: wave5: Release m2m_ctx after Instance Removed from List

Possible use after free if IRQ thread manages to obtain spinlock between m2m_ctx release and wave5_release function removing stream instance from list of active instances. The IRQ thread looks for the m2m_ctx which is freed so null pointer dereference occurs.

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
1st
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 28, 2026

Advisory Details (2)

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

media: chips-media: wave5: Release m2m_ctx after Instance Removed from List - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7cdbd7bb21949a8fda10c7104a2b12ee363cbf5c
generic

media: chips-media: wave5: Release m2m_ctx after Instance Removed from List - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04cda0b5c4ca3f61cbc86e41ead3c462c8cfd659

Vendor Advisories for CVE-2026-97513(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (177 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-97513?
CVE-2026-97513 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Release m2m_ctx after Instance Removed from List Possible use after free if IRQ thread manages to obtain spinlock between m2mctx release and wave5release function removing stream instance from list of…
When was CVE-2026-97513 disclosed?
CVE-2026-97513 was first published on September 24, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97513 actively exploited?
CVE-2026-97513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97513?
CVE-2026-97513 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-97513?
No fix for CVE-2026-97513 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-97513 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-97513

Explore →

Is Your Infrastructure Affected by CVE-2026-97513?

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

Book a Demo →Browse All CVEs