<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T15:25:47.098632+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-74372</id>
    <title>CVE-2026-74372 — raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path</title>
    <updated>2026-10-02T15:25:47.411967+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>raid1: fix nr_pending leak in REQ_ATOMIC bad-block error path</p>
<p>In raid1_write_request(), each per-mirror loop iteration begins by
incrementing rdev-&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.</p>
<p>err_handle's cleanup loop will only decrements for k &lt; i and
r1_bio-&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 &gt; 0.</p>
<p>Fix this by calling rdev_dec_pending() before jumping to err_handle.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74372"/>
  </entry>
</feed>
