<?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 23:48:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68317 — pds_core: fix auxiliary device add/del races</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68317</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;pds_core: fix auxiliary device add/del races&lt;/p&gt;
&lt;p&gt;Two paths add or delete the same slot (pf-&amp;gt;vfs[vf_id].padev): a VF&amp;#39;s
pdsc_reset_done() and the PF&amp;#39;s devlink enable_vnet/disable_vnet handler.
They serialize on config_lock, but neither guards the slot under it
correctly.&lt;/p&gt;
&lt;p&gt;add() registers and stores a new auxiliary device without first checking
the slot, so a second add of an already-populated slot leaks the first
device. del() makes that check outside config_lock, so two concurrent
dels can both pass it; the first clears the slot, and the second
dereferences a NULL pointer.&lt;/p&gt;
&lt;p&gt;Check and update the slot under config_lock in both paths.&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;pds_core: fix auxiliary device add/del races&lt;/p&gt;
&lt;p&gt;Two paths add or delete the same slot (pf-&amp;gt;vfs[vf_id].padev): a VF&amp;#39;s
pdsc_reset_done() and the PF&amp;#39;s devlink enable_vnet/disable_vnet handler.
They serialize on config_lock, but neither guards the slot under it
correctly.&lt;/p&gt;
&lt;p&gt;add() registers and stores a new auxiliary device without first checking
the slot, so a second add of an already-populated slot leaks the first
device. del() makes that check outside config_lock, so two concurrent
dels can both pass it; the first clears the slot, and the second
dereferences a NULL pointer.&lt;/p&gt;
&lt;p&gt;Check and update the slot under config_lock in both paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68317</guid>
    </item>
  </channel>
</rss>
