<?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://cve.radiocsirt.org</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>Fri, 09 Oct 2026 22:20:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98266 — ALSA: core: Fix potential UAF after asynchronous card release</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-98266</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: core: Fix potential UAF after asynchronous card release&lt;/p&gt;
&lt;p&gt;Usually a sound driver releases the resources assigned to the card via
snd_card_free(), and it synchronizes with the whole release procedure.
However, when the card is released asynchronously via
snd_card_free_when_closed() like USB-audio driver, the situation is
slightly different; although the snd_card_disconnect() call at the
disconnection guarantees that any newer accesses will be gated, the
in-flight tasks might be still accessing to the underlying card-&amp;gt;dev
device even after the disconnection, which would cause a
use-after-free in the end, as reported by fuzzers.&lt;/p&gt;
&lt;p&gt;For addressing the bug above, this patch takes the refcount of
card-&amp;gt;dev at initialization of the card object, and releases at its
destructor.   This assures the availability of the card-&amp;gt;dev in its
whole lifecycle.&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: core: Fix potential UAF after asynchronous card release&lt;/p&gt;
&lt;p&gt;Usually a sound driver releases the resources assigned to the card via
snd_card_free(), and it synchronizes with the whole release procedure.
However, when the card is released asynchronously via
snd_card_free_when_closed() like USB-audio driver, the situation is
slightly different; although the snd_card_disconnect() call at the
disconnection guarantees that any newer accesses will be gated, the
in-flight tasks might be still accessing to the underlying card-&amp;gt;dev
device even after the disconnection, which would cause a
use-after-free in the end, as reported by fuzzers.&lt;/p&gt;
&lt;p&gt;For addressing the bug above, this patch takes the refcount of
card-&amp;gt;dev at initialization of the card object, and releases at its
destructor.   This assures the availability of the card-&amp;gt;dev in its
whole lifecycle.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-98266</guid>
    </item>
  </channel>
</rss>
