<?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>Thu, 01 Oct 2026 05:33:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43120 — RDMA/irdma: Fix double free related to rereg_user_mr</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43120</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/irdma: Fix double free related to rereg_user_mr&lt;/p&gt;
&lt;p&gt;If IB_MR_REREG_TRANS is set during rereg_user_mr, the
umem will be released and a new one will be allocated
in irdma_rereg_mr_trans. If any step of irdma_rereg_mr_trans
fails after the new umem is allocated, it releases the umem,
but does not set iwmr-&amp;gt;region to NULL. The problem is that
this failure is propagated to the user, who will then call
ibv_dereg_mr (as they should). Then, the dereg_mr path will
see a non-NULL umem and attempt to call ib_umem_release again.&lt;/p&gt;
&lt;p&gt;Fix this by setting iwmr-&amp;gt;region to NULL after ib_umem_release.&lt;/p&gt;
&lt;p&gt;Fixed: 5ac388db27c4 (&amp;#34;RDMA/irdma: Add support to re-register a memory region&amp;#34;)&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/irdma: Fix double free related to rereg_user_mr&lt;/p&gt;
&lt;p&gt;If IB_MR_REREG_TRANS is set during rereg_user_mr, the
umem will be released and a new one will be allocated
in irdma_rereg_mr_trans. If any step of irdma_rereg_mr_trans
fails after the new umem is allocated, it releases the umem,
but does not set iwmr-&amp;gt;region to NULL. The problem is that
this failure is propagated to the user, who will then call
ibv_dereg_mr (as they should). Then, the dereg_mr path will
see a non-NULL umem and attempt to call ib_umem_release again.&lt;/p&gt;
&lt;p&gt;Fix this by setting iwmr-&amp;gt;region to NULL after ib_umem_release.&lt;/p&gt;
&lt;p&gt;Fixed: 5ac388db27c4 (&amp;#34;RDMA/irdma: Add support to re-register a memory region&amp;#34;)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43120</guid>
    </item>
  </channel>
</rss>
