<?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>Fri, 02 Oct 2026 14:10:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74334 — RDMA/nldev: Fix locking when accessing mr-&gt;pd</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74334</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;RDMA/nldev: Fix locking when accessing mr-&amp;gt;pd&lt;/p&gt;
&lt;p&gt;Sashiko points out that, due to rereg_mr, the PD is actually variable and
all the touches in nldev are racy.&lt;/p&gt;
&lt;p&gt;Use mr-&amp;gt;device instead of mr-&amp;gt;pd-&amp;gt;device.&lt;/p&gt;
&lt;p&gt;Getting the PD restrack ID is more tricky. To avoid disturbing all the
happy paths, add an rdma_restrack_sync() operation which is sort of like
flush_workqueue() or synchronize_irq(): after it returns, all the old
nldev touches to the mr are gone and everything sees the new PD. This
makes it safe to reach into the PD pointer.&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;RDMA/nldev: Fix locking when accessing mr-&amp;gt;pd&lt;/p&gt;
&lt;p&gt;Sashiko points out that, due to rereg_mr, the PD is actually variable and
all the touches in nldev are racy.&lt;/p&gt;
&lt;p&gt;Use mr-&amp;gt;device instead of mr-&amp;gt;pd-&amp;gt;device.&lt;/p&gt;
&lt;p&gt;Getting the PD restrack ID is more tricky. To avoid disturbing all the
happy paths, add an rdma_restrack_sync() operation which is sort of like
flush_workqueue() or synchronize_irq(): after it returns, all the old
nldev touches to the mr are gone and everything sees the new PD. This
makes it safe to reach into the PD pointer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74334</guid>
    </item>
  </channel>
</rss>
