<?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-10-02T14:10:14.238013+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-74334</id>
    <title>CVE-2026-74334 — RDMA/nldev: Fix locking when accessing mr-&gt;pd</title>
    <updated>2026-10-02T14:10:15.259201+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>RDMA/nldev: Fix locking when accessing mr-&gt;pd</p>
<p>Sashiko points out that, due to rereg_mr, the PD is actually variable and
all the touches in nldev are racy.</p>
<p>Use mr-&gt;device instead of mr-&gt;pd-&gt;device.</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74334"/>
  </entry>
</feed>
