<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 06:55:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80716 — ALSA: pcm: wake linked drain waiters on unlink</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80716</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: pcm: wake linked drain waiters on unlink&lt;/p&gt;
&lt;p&gt;snd_pcm_drain() on a linked stream parks an on-stack wait entry on the
drained peer&amp;#39;s runtime-&amp;gt;sleep, and after schedule_timeout() removes it
only if that peer is still found in the caller&amp;#39;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Unlike the close path (snd_pcm_drop() -&amp;gt; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ALSA: pcm: wake linked drain waiters on unlink&lt;/p&gt;
&lt;p&gt;snd_pcm_drain() on a linked stream parks an on-stack wait entry on the
drained peer&amp;#39;s runtime-&amp;gt;sleep, and after schedule_timeout() removes it
only if that peer is still found in the caller&amp;#39;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;Unlike the close path (snd_pcm_drop() -&amp;gt; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80716</guid>
    </item>
  </channel>
</rss>
