<?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>Tue, 29 Sep 2026 00:47:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31399 — nvdimm/bus: Fix potential use after free in asynchronous initialization</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31399</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;nvdimm/bus: Fix potential use after free in asynchronous initialization&lt;/p&gt;
&lt;p&gt;Dingisoul with KASAN reports a use after free if device_add() fails in
nd_async_device_register().&lt;/p&gt;
&lt;p&gt;Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while
scheduling async init&amp;#34;) correctly added a reference on the parent device
to be held until asynchronous initialization was complete.  However, if
device_add() results in an allocation failure the ref count of the
device drops to 0 prior to the parent pointer being accessed.  Thus
resulting in use after free.&lt;/p&gt;
&lt;p&gt;The bug bot AI correctly identified the fix.  Save a reference to the
parent pointer to be used to drop the parent reference regardless of the
outcome of device_add().&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;nvdimm/bus: Fix potential use after free in asynchronous initialization&lt;/p&gt;
&lt;p&gt;Dingisoul with KASAN reports a use after free if device_add() fails in
nd_async_device_register().&lt;/p&gt;
&lt;p&gt;Commit b6eae0f61db2 (&amp;#34;libnvdimm: Hold reference on parent while
scheduling async init&amp;#34;) correctly added a reference on the parent device
to be held until asynchronous initialization was complete.  However, if
device_add() results in an allocation failure the ref count of the
device drops to 0 prior to the parent pointer being accessed.  Thus
resulting in use after free.&lt;/p&gt;
&lt;p&gt;The bug bot AI correctly identified the fix.  Save a reference to the
parent pointer to be used to drop the parent reference regardless of the
outcome of device_add().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31399</guid>
    </item>
  </channel>
</rss>
