CVE-2026-97575

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. 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.2%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: v4l2-ctrls: validate AV1 tile counts

The stateless AV1 decoders use tile_info.tile_cols and tile_rows as loop bounds and as indices into the mi_*_starts[] and *_in_sbs_minus_1[] arrays, as the divisor for context_update_tile_id, and their product bounds the per-tile descriptor buffers, but std_validate_compound() does not bound these u8 fields. Reject a V4L2_CTRL_TYPE_AV1_FRAME whose tile_cols or tile_rows exceeds V4L2_AV1_MAX_TILE_COLS / _ROWS, or whose product exceeds V4L2_AV1_MAX_TILE_COUNT. A zero tile count is left to the consuming driver so the zero-initialised control that existing userspace submits is still accepted.

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.2%
EPSS %ILE
4th
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 25, 2026

Last Modified

October 3, 2026

Advisory Details (4)

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

media: v4l2-ctrls: validate AV1 tile counts - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/439058ced617fbb3febc017b9e93bb7387f309e0
generic

media: v4l2-ctrls: validate AV1 tile counts - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: v4l2-ctrls: validate AV1 tile counts - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: v4l2-ctrls: validate AV1 tile counts - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85df9fc79b07f1cc7c953f930ae7e675d0c1e820

Vendor Advisories for CVE-2026-97575(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
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 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-97575?
CVE-2026-97575 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: media: v4l2-ctrls: validate AV1 tile counts The stateless AV1 decoders use tileinfo.tilecols and tile_rows as loop bounds and as indices into the mi*starts[] and *insbsminus1[] arrays, as the divisor for contextupdatetile_id, and…
When was CVE-2026-97575 disclosed?
CVE-2026-97575 was first published on September 25, 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-97575 actively exploited?
CVE-2026-97575 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97575?
CVE-2026-97575 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-97575?
No fix for CVE-2026-97575 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-97575 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-97575

Explore →

Is Your Infrastructure Affected by CVE-2026-97575?

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