CVE-2026-80716

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. 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:

ALSA: pcm: wake linked drain waiters on unlink

snd_pcm_drain() on a linked stream parks an on-stack wait entry on the drained peer's runtime->sleep, and after schedule_timeout() removes it only if that peer is still found in the caller's group. If group membership changes during the wait and the sleep ends by signal or timeout (so autoremove_wake_function() does not run), finish_wait() is skipped and snd_pcm_drain() returns with the entry still queued on that stream's sleep list; a later wake_up() then walks a freed stack frame. This is reachable by unlinking either the drained or the draining stream.

Unlike the close path (snd_pcm_drop() -> snd_pcm_post_stop()), snd_pcm_unlink() never wakes the sleep queues. Wake every group member under the group lock before the membership change, so a linked drainer is released and drops its entry while the streams are still grouped.

The window was opened when snd_pcm_link_rwsem stopped being held across the wait and the removal became conditional on group membership (see Fixes). The later switch to finish_wait() kept that conditional removal, so the signal/timeout case remained.

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
2%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (8)

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

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2940cc3cf43c72126b74ee6376314c195382023a
generic

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

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

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3035bb784cea3f338934f5042dd3f35225a51b2e
generic

ALSA: pcm: wake linked drain waiters on unlink - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c172e4c53321ee6429955295ea133bc3597a3ca9

Vendor Advisories for CVE-2026-80716(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 12× in last 7d / 12× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 20:18 UTCEG score recompute
  3. 2026-08-29 20:18 UTCGHSA enrichment
  4. 2026-08-29 07:25 UTCEG score recompute
  5. 2026-08-29 07:24 UTCGHSA enrichment
  6. 2026-08-29 06:35 UTCEG score recompute 7.80
  7. 2026-08-29 06:35 UTCGHSA enrichment
  8. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  9. 2026-08-28 21:42 UTCEPSS rescore
  10. 2026-08-28 08:20 UTCNVD update
  11. 2026-08-28 07:33 UTCEG score recompute
  12. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80716?
CVE-2026-80716 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: wake linked drain waiters on unlink sndpcmdrain() on a linked stream parks an on-stack wait entry on the drained peer's runtime->sleep, and after schedule_timeout() removes it only if that peer is still found in the…
When was CVE-2026-80716 disclosed?
CVE-2026-80716 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80716 actively exploited?
CVE-2026-80716 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 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-80716?
CVE-2026-80716 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80716?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80716, 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-80716

Explore →

Is Your Infrastructure Affected by CVE-2026-80716?

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