<?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://db.gcve.eu</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, 20 Nov 2026 21:22:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99597 — srcu: Add list_splice_init_srcu()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99597</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;srcu: Add list_splice_init_srcu()&lt;/p&gt;
&lt;p&gt;list_splice_init_rcu() makes a list look empty to new readers, waits for
the current ones with the given sync function, and only then links the
entries into the new list. The sync function takes no argument, so it
can wait for RCU readers but not for the readers of an srcu_struct.&lt;/p&gt;
&lt;p&gt;Passing synchronize_rcu() for a list read under SRCU still builds, but
leaves SRCU readers on the entries while the last one&amp;#39;s next pointer is
moved onto the new list head. nvme_remove_namespaces() does this today.&lt;/p&gt;
&lt;p&gt;Add list_splice_init_srcu(), which waits for the readers of the given
srcu_struct instead.&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;srcu: Add list_splice_init_srcu()&lt;/p&gt;
&lt;p&gt;list_splice_init_rcu() makes a list look empty to new readers, waits for
the current ones with the given sync function, and only then links the
entries into the new list. The sync function takes no argument, so it
can wait for RCU readers but not for the readers of an srcu_struct.&lt;/p&gt;
&lt;p&gt;Passing synchronize_rcu() for a list read under SRCU still builds, but
leaves SRCU readers on the entries while the last one&amp;#39;s next pointer is
moved onto the new list head. nvme_remove_namespaces() does this today.&lt;/p&gt;
&lt;p&gt;Add list_splice_init_srcu(), which waits for the readers of the given
srcu_struct instead.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99597</guid>
    </item>
  </channel>
</rss>
