<?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>Fri, 02 Oct 2026 15:25:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74372 — raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74372</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;raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path&lt;/p&gt;
&lt;p&gt;In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a
badblock within the requested range, the code jumps to err_handle
without dropping the reference taken for the current mirror.&lt;/p&gt;
&lt;p&gt;err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and
r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped,
leaving its nr_pending reference leaked permanently. The reference
prevents the rdev from ever being removed, since raid1_remove_conf()
refuses to remove an rdev with nr_pending &amp;gt; 0.&lt;/p&gt;
&lt;p&gt;Fix this by calling rdev_dec_pending() before jumping to err_handle.&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;raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path&lt;/p&gt;
&lt;p&gt;In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev-&amp;gt;nr_pending. If a REQ_ATOMIC write encounters a
badblock within the requested range, the code jumps to err_handle
without dropping the reference taken for the current mirror.&lt;/p&gt;
&lt;p&gt;err_handle&amp;#39;s cleanup loop will only decrements for k &amp;lt; i and
r1_bio-&amp;gt;bios[k] is non-NULL. The current slot is therefore skipped,
leaving its nr_pending reference leaked permanently. The reference
prevents the rdev from ever being removed, since raid1_remove_conf()
refuses to remove an rdev with nr_pending &amp;gt; 0.&lt;/p&gt;
&lt;p&gt;Fix this by calling rdev_dec_pending() before jumping to err_handle.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74372</guid>
    </item>
  </channel>
</rss>
