<?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>Wed, 07 Oct 2026 10:15:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47281 — ALSA: seq: Fix race of snd_seq_timer_open()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47281</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: seq: Fix race of snd_seq_timer_open()&lt;/p&gt;
&lt;p&gt;The timer instance per queue is exclusive, and snd_seq_timer_open()
should have managed the concurrent accesses.  It looks as if it&amp;#39;s
checking the already existing timer instance at the beginning, but
it&amp;#39;s not right, because there is no protection, hence any later
concurrent call of snd_seq_timer_open() may override the timer
instance easily.  This may result in UAF, as the leftover timer
instance can keep running while the queue itself gets closed, as
spotted by syzkaller recently.&lt;/p&gt;
&lt;p&gt;For avoiding the race, add a proper check at the assignment of
tmr-&amp;gt;timeri again, and return -EBUSY if it&amp;#39;s been already registered.&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: seq: Fix race of snd_seq_timer_open()&lt;/p&gt;
&lt;p&gt;The timer instance per queue is exclusive, and snd_seq_timer_open()
should have managed the concurrent accesses.  It looks as if it&amp;#39;s
checking the already existing timer instance at the beginning, but
it&amp;#39;s not right, because there is no protection, hence any later
concurrent call of snd_seq_timer_open() may override the timer
instance easily.  This may result in UAF, as the leftover timer
instance can keep running while the queue itself gets closed, as
spotted by syzkaller recently.&lt;/p&gt;
&lt;p&gt;For avoiding the race, add a proper check at the assignment of
tmr-&amp;gt;timeri again, and return -EBUSY if it&amp;#39;s been already registered.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47281</guid>
    </item>
  </channel>
</rss>
