CVE-2026-72302

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

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

ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc

In sof_ipc3_control_update(), the expected_size calculation uses firmware-provided cdata->num_elems in arithmetic that could overflow on 32-bit platforms, wrapping to a small value. This would allow the cdata->rhdr.hdr.size comparison to pass with mismatched sizes, potentially leading to out-of-bounds access in snd_sof_update_control.

Use check_mul_overflow() and check_add_overflow() to detect and reject overflowed size calculations.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (6)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89a2309a9eec80d4c19e3aed62c4f923594d1911
generic

ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8791977d7289f6e9d2b014f60a5455f053a7bc04
generic

ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/711d912b18763af62a63aa8f2419a774eb63bba4
generic

ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6856b3c23b0995eefad5a6142b4365ef70e1fe4a
generic

ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/312c7d2ebe696da3f885eee77d52297664e57c53

Vendor Advisories for CVE-2026-72302(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 30× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 19:21 UTCGHSA enrichment
  3. 2026-08-20 07:19 UTCGHSA enrichment
  4. 2026-08-19 19:17 UTCEG score recompute
  5. 2026-08-19 19:17 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 07:11 UTCGHSA enrichment
  8. 2026-08-18 19:07 UTCEG score recompute
  9. 2026-08-18 19:07 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:03 UTCGHSA enrichment
  13. 2026-08-17 19:00 UTCEG score recompute
  14. 2026-08-17 19:00 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:19 UTCEG score recompute
  17. 2026-08-17 06:19 UTCGHSA enrichment
  18. 2026-08-17 05:59 UTCEG score recompute▲ 7.80
  19. 2026-08-17 05:59 UTCGHSA enrichment
  20. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  21. 2026-08-17 05:30 UTCEG score recompute
  22. 2026-08-17 05:30 UTCGHSA enrichment
  23. 2026-08-17 05:24 UTCMITRE cvelistV5
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 5 more
  1. 2026-08-16 02:15 UTCEPSS rescore
  2. 2026-08-15 06:37 UTCGHSA enrichment
  3. 2026-08-15 06:23 UTCNVD update
  4. 2026-08-15 06:07 UTCEG score recompute
  5. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72302?
CVE-2026-72302 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc In sofipc3controlupdate(), the expectedsize calculation uses firmware-provided cdata->num_elems in arithmetic that could overflow on 32-bit platforms,…
When was CVE-2026-72302 disclosed?
CVE-2026-72302 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72302 actively exploited?
CVE-2026-72302 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.4% of all scored CVEs.
What is the CVSS score of CVE-2026-72302?
CVE-2026-72302 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72302?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72302, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72302

Explore →

Is Your Infrastructure Affected by CVE-2026-72302?

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

Start Free Scan →Browse All CVEs