CVE-2026-80716

ALSA: pcm: wake linked drain waiters on unlink

HIGH
7.8
CVSS Score
Published: August 28, 2026 at 06:53 AM UTC
Updated: October 16, 2026 at 08:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.1f57f3df03a8e6010e321fa0258d3e054713c3cb7
Vendor states this is fixed in 1c1b7e8e545ce65e40f65b55c432765e058ea98f (fixed)
Vendor states this is fixed in 2940cc3cf43c72126b74ee6376314c195382023a (fixed)
Vendor states this is fixed in 3035bb784cea3f338934f5042dd3f35225a51b2e (fixed)
Vendor states this is fixed in c172e4c53321ee6429955295ea133bc3597a3ca9 (fixed)
Vendor states this is fixed in db09bc4ab19ce548a078240d2374792523953500 (fixed)
Vendor states this is fixed in e8315330e4ec09c0cac625515400e13d0ee22b81 (fixed)
Vendor states this is fixed in e8b784a3f4fba3ea9c4d05138ecfa784a069627f (fixed)
Vendor states this is fixed in f495b6c4c8594122918552c9be2b51eb71647cd9 (fixed)
Vendor states this is fixed in 5.1 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card