<?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 07:10:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21732 — RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21732</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/mlx5: Fix a race for an ODP MR which leads to CQE with error&lt;/p&gt;
&lt;p&gt;This patch addresses a race condition for an ODP MR that can result in a
CQE with an error on the UMR QP.&lt;/p&gt;
&lt;p&gt;During the __mlx5_ib_dereg_mr() flow, the following sequence of calls
occurs:&lt;/p&gt;
&lt;p&gt;mlx5_revoke_mr()
 mlx5r_umr_revoke_mr()
 mlx5r_umr_post_send_wait()&lt;/p&gt;
&lt;p&gt;At this point, the lkey is freed from the hardware&amp;#39;s perspective.&lt;/p&gt;
&lt;p&gt;However, concurrently, mlx5_ib_invalidate_range() might be triggered by
another task attempting to invalidate a range for the same freed lkey.&lt;/p&gt;
&lt;p&gt;This task will:
 - Acquire the umem_odp-&amp;gt;umem_mutex lock.
 - Call mlx5r_umr_update_xlt() on the UMR QP.
 - Since the lkey has already been freed, this can lead to a CQE error,
   causing the UMR QP to enter an error state [1].&lt;/p&gt;
&lt;p&gt;To resolve this race condition, the umem_odp-&amp;gt;umem_mutex lock is now also
acquired as part of the mlx5_revoke_mr() scope.  Upon successful revoke,
we set umem_odp-&amp;gt;private which points to that MR to NULL, preventing any
further invalidation attempts on its lkey.&lt;/p&gt;
&lt;p&gt;[1] From dmesg:&lt;/p&gt;
&lt;p&gt;infiniband rocep8s0f0: dump_cqe:277:(pid 0): WC error: 6, Message: memory bind operation error
   cqe_dump: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   cqe_dump: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   cqe_dump: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   cqe_dump: 00000030: 00 00 00 00 08 00 78 06 25 00 11 b9 00 0e dd d2&lt;/p&gt;
&lt;p&gt;WA…&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/mlx5: Fix a race for an ODP MR which leads to CQE with error&lt;/p&gt;
&lt;p&gt;This patch addresses a race condition for an ODP MR that can result in a
CQE with an error on the UMR QP.&lt;/p&gt;
&lt;p&gt;During the __mlx5_ib_dereg_mr() flow, the following sequence of calls
occurs:&lt;/p&gt;
&lt;p&gt;mlx5_revoke_mr()
 mlx5r_umr_revoke_mr()
 mlx5r_umr_post_send_wait()&lt;/p&gt;
&lt;p&gt;At this point, the lkey is freed from the hardware&amp;#39;s perspective.&lt;/p&gt;
&lt;p&gt;However, concurrently, mlx5_ib_invalidate_range() might be triggered by
another task attempting to invalidate a range for the same freed lkey.&lt;/p&gt;
&lt;p&gt;This task will:
 - Acquire the umem_odp-&amp;gt;umem_mutex lock.
 - Call mlx5r_umr_update_xlt() on the UMR QP.
 - Since the lkey has already been freed, this can lead to a CQE error,
   causing the UMR QP to enter an error state [1].&lt;/p&gt;
&lt;p&gt;To resolve this race condition, the umem_odp-&amp;gt;umem_mutex lock is now also
acquired as part of the mlx5_revoke_mr() scope.  Upon successful revoke,
we set umem_odp-&amp;gt;private which points to that MR to NULL, preventing any
further invalidation attempts on its lkey.&lt;/p&gt;
&lt;p&gt;[1] From dmesg:&lt;/p&gt;
&lt;p&gt;infiniband rocep8s0f0: dump_cqe:277:(pid 0): WC error: 6, Message: memory bind operation error
   cqe_dump: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   cqe_dump: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   cqe_dump: 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   cqe_dump: 00000030: 00 00 00 00 08 00 78 06 25 00 11 b9 00 0e dd d2&lt;/p&gt;
&lt;p&gt;WA…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21732</guid>
    </item>
  </channel>
</rss>
