<?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-09-29T04:55:28.276085+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-89972</id>
    <title>CVE-2026-89972 — nvme: add missing SRCU grace period in error path</title>
    <updated>2026-09-29T04:55:28.531591+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>nvme: add missing SRCU grace period in error path</p>
<p>nvme_alloc_ns() error path at out_unlink_ns removes ns from the
namespace head siblings list with list_del_rcu(&amp;ns-&gt;siblings) but
does not wait for SRCU readers before freeing the namespace struct.
Multipath code iterates the head-&gt;list under srcu_read_lock() in
nvme_find_path() and nvme_mpath_revalidate_paths(), so a concurrent
reader can still hold a reference to ns when kfree(ns) runs.</p>
<p>The normal removal path in nvme_ns_remove() correctly calls
synchronize_srcu(&amp;ns-&gt;head-&gt;srcu) after list_del_rcu() to wait for
in-progress readers. Add the same grace period in the error path.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89972"/>
  </entry>
</feed>
