CVE-2026-80716
CVE CVE-2026-80716EUVD EUVD-2026-67451Published 2026-08-28T06:53:14.000ZLast changed 2026-08-29T06:22:32.000ZCVSS 7.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux f57f3df03a8e6010e321fa0258d3e054713c3cb7 <e8b784a3f4fba3ea9c4d05138ecfa784a069627f; f57f3df03a8e6010e321fa0258d3e054713c3cb7 <e8315330e4ec09c0cac625515400e13d0ee22b81; f57f3df03a8e6010e321fa0258d3e054713c3cb7 <3035bb784cea3f338934f5042dd3f35225a51b2e; f57f3df03a8e6010e321fa0258d3e054713c3cb7 <f495b6c4c8594122918552c9be2b51eb71647cd9; f57f3df03a8e6010e321fa0258d3e054713c3cb7 <c172e4c53321ee6429955295ea133bc3597a3ca9; patch: 7.1.8; f57f3df03a8e6010e321fa0258d3e054713c3cb7 <db09bc4ab19ce548a078240d2374792523953500; patch: 5.10.265; patch: 6.1.183; patch: 6.18.44; patch: 0; f57f3df03a8e6010e321fa0258d3e054713c3cb7 <1c1b7e8e545ce65e40f65b55c432765e058ea98f; patch: 6.12.103; patch: 6.6.151; patch: 5.15.216; patch: 7.2; 5.1; f57f3df03a8e6010e321fa0258d3e054713c3cb7 <2940cc3cf43c72126b74ee6376314c195382023a
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.