<?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>Mon, 05 Oct 2026 11:48:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47646 — Revert "Revert "block, bfq: honor already-setup queue merges""</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47646</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;Revert &amp;#34;Revert &amp;#34;block, bfq: honor already-setup queue merges&amp;#34;&amp;#34;&lt;/p&gt;
&lt;p&gt;A crash [1] happened to be triggered in conjunction with commit
2d52c58b9c9b (&amp;#34;block, bfq: honor already-setup queue merges&amp;#34;). The
latter was then reverted by commit ebc69e897e17 (&amp;#34;Revert &amp;#34;block, bfq:
honor already-setup queue merges&amp;#34;&amp;#34;). Yet, the reverted commit was not
the one introducing the bug. In fact, it actually triggered a UAF
introduced by a different commit, and now fixed by commit d29bd41428cf
(&amp;#34;block, bfq: reset last_bfqq_created on group change&amp;#34;).&lt;/p&gt;
&lt;p&gt;So, there is no point in keeping commit 2d52c58b9c9b (&amp;#34;block, bfq:
honor already-setup queue merges&amp;#34;) out. This commit restores it.&lt;/p&gt;
&lt;p&gt;[1] https://bugzilla.kernel.org/show_bug.cgi?id=214503&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;Revert &amp;#34;Revert &amp;#34;block, bfq: honor already-setup queue merges&amp;#34;&amp;#34;&lt;/p&gt;
&lt;p&gt;A crash [1] happened to be triggered in conjunction with commit
2d52c58b9c9b (&amp;#34;block, bfq: honor already-setup queue merges&amp;#34;). The
latter was then reverted by commit ebc69e897e17 (&amp;#34;Revert &amp;#34;block, bfq:
honor already-setup queue merges&amp;#34;&amp;#34;). Yet, the reverted commit was not
the one introducing the bug. In fact, it actually triggered a UAF
introduced by a different commit, and now fixed by commit d29bd41428cf
(&amp;#34;block, bfq: reset last_bfqq_created on group change&amp;#34;).&lt;/p&gt;
&lt;p&gt;So, there is no point in keeping commit 2d52c58b9c9b (&amp;#34;block, bfq:
honor already-setup queue merges&amp;#34;) out. This commit restores it.&lt;/p&gt;
&lt;p&gt;[1] https://bugzilla.kernel.org/show_bug.cgi?id=214503&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47646</guid>
    </item>
  </channel>
</rss>
