CVE-2026-72262

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: Fix heap overflow in bytes_ext put/get

The ipc_control_data buffer is allocated as kzalloc(max_size), where max_size covers the entire struct sof_ipc_ctrl_data including its flexible array payload. However, the bounds checks in bytes_ext_put and _bytes_ext_get compared user data lengths against max_size directly, ignoring that cdata->data sits at an offset of sizeof(struct sof_ipc_ctrl_data) bytes into the allocation.

This allowed writing up to sizeof(struct sof_ipc_ctrl_data) bytes past the end of the heap buffer from unprivileged userspace via the ALSA TLV kcontrol interface, and similarly allowed over-reading adjacent heap data on the get path.

Fix all bounds checks to subtract sizeof(*cdata) from max_size so they reflect the actual space available at the cdata->data offset. Also fix the error-path restore in bytes_ext_put which wrote to cdata->data instead of cdata, causing the same overflow.

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 (5)

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

ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1adde1941bba7b0d7104b86ed819d48d81cb0ad9
generic

ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/121577383b5cf221e86581e0f2bcca4c66f17469

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

Frequently asked(5)

What is CVE-2026-72262?
CVE-2026-72262 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get The ipccontroldata buffer is allocated as kzalloc(max_size), where maxsize covers the entire struct sofipcctrldata including its flexible array payload. However, the…
When was CVE-2026-72262 disclosed?
CVE-2026-72262 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-72262 actively exploited?
CVE-2026-72262 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-72262?
CVE-2026-72262 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72262, 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-72262

Explore →

Is Your Infrastructure Affected by CVE-2026-72262?

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