<?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:14:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38373 — IB/mlx5: Fix potential deadlock in MR deregistration</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38373</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;IB/mlx5: Fix potential deadlock in MR deregistration&lt;/p&gt;
&lt;p&gt;The issue arises when kzalloc() is invoked while holding umem_mutex or
any other lock acquired under umem_mutex. This is problematic because
kzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke
mmu_notifier_invalidate_range_start(). This function can lead to
mlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,
resulting in a deadlock.&lt;/p&gt;
&lt;p&gt;The problematic flow:
             CPU0                      |              CPU1
---------------------------------------|------------------------------------------------
mlx5_ib_dereg_mr()                     |
 → revoke_mr()                         |
   → mutex_lock(&amp;amp;umem_odp-&amp;gt;umem_mutex) |
                                       | mlx5_mkey_cache_init()
                                       |  → mutex_lock(&amp;amp;dev-&amp;gt;cache.rb_lock)
                                       |  → mlx5r_cache_create_ent_locked()
                                       |    → kzalloc(GFP_KERNEL)
                                       |      → fs_reclaim()
                                       |        → mmu_notifier_invalidate_range_start()
                                       |          → mlx5_ib_invalidate_range()
                                       |            → mutex_lock(&amp;amp;umem_odp-&amp;gt;umem_mutex)
   → cache_ent_find_and_store()        |
     → mutex_lock(&amp;amp;dev-&amp;gt;cache.rb_lock) |&lt;/p&gt;
&lt;p&gt;Additionally, when kzalloc(…&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;IB/mlx5: Fix potential deadlock in MR deregistration&lt;/p&gt;
&lt;p&gt;The issue arises when kzalloc() is invoked while holding umem_mutex or
any other lock acquired under umem_mutex. This is problematic because
kzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke
mmu_notifier_invalidate_range_start(). This function can lead to
mlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,
resulting in a deadlock.&lt;/p&gt;
&lt;p&gt;The problematic flow:
             CPU0                      |              CPU1
---------------------------------------|------------------------------------------------
mlx5_ib_dereg_mr()                     |
 → revoke_mr()                         |
   → mutex_lock(&amp;amp;umem_odp-&amp;gt;umem_mutex) |
                                       | mlx5_mkey_cache_init()
                                       |  → mutex_lock(&amp;amp;dev-&amp;gt;cache.rb_lock)
                                       |  → mlx5r_cache_create_ent_locked()
                                       |    → kzalloc(GFP_KERNEL)
                                       |      → fs_reclaim()
                                       |        → mmu_notifier_invalidate_range_start()
                                       |          → mlx5_ib_invalidate_range()
                                       |            → mutex_lock(&amp;amp;umem_odp-&amp;gt;umem_mutex)
   → cache_ent_find_and_store()        |
     → mutex_lock(&amp;amp;dev-&amp;gt;cache.rb_lock) |&lt;/p&gt;
&lt;p&gt;Additionally, when kzalloc(…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38373</guid>
    </item>
  </channel>
</rss>
