<?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://db.gcve.eu</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>Sat, 17 Oct 2026 19:49:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98253 — RDMA/ucma: Serialize join and leave on copy_to_user failure</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98253</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/ucma: Serialize join and leave on copy_to_user failure&lt;/p&gt;
&lt;p&gt;rdma_join_multicast() queues RoCE work that later reads the ucma_multicast
through event-&amp;gt;param.ud.private_data, then list_add()s the CMA multicast
at the head of id_priv-&amp;gt;mc_list. rdma_leave_multicast() matches only by
sockaddr and destroys the first hit.&lt;/p&gt;
&lt;p&gt;ucma_process_join() used to drop ctx-&amp;gt;mutex after a successful join and
retake it only if copy_to_user() failed. Two concurrent JOIN_MCAST calls
with the same address can therefore insert a second CMA entry before the
first thread&amp;#39;s leave. leave then cancels the newer work and the older
worker still dereferences the ucma_multicast that the first thread frees.&lt;/p&gt;
&lt;p&gt;Keep ctx-&amp;gt;mutex held from rdma_join_multicast() through copy_to_user() and,
on -EFAULT, through rdma_leave_multicast() so leave cannot miss this join.
Do not leave if join itself failed: that path never published this address
on mc_list, and a leave-by-addr would destroy an earlier successful join.&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/ucma: Serialize join and leave on copy_to_user failure&lt;/p&gt;
&lt;p&gt;rdma_join_multicast() queues RoCE work that later reads the ucma_multicast
through event-&amp;gt;param.ud.private_data, then list_add()s the CMA multicast
at the head of id_priv-&amp;gt;mc_list. rdma_leave_multicast() matches only by
sockaddr and destroys the first hit.&lt;/p&gt;
&lt;p&gt;ucma_process_join() used to drop ctx-&amp;gt;mutex after a successful join and
retake it only if copy_to_user() failed. Two concurrent JOIN_MCAST calls
with the same address can therefore insert a second CMA entry before the
first thread&amp;#39;s leave. leave then cancels the newer work and the older
worker still dereferences the ucma_multicast that the first thread frees.&lt;/p&gt;
&lt;p&gt;Keep ctx-&amp;gt;mutex held from rdma_join_multicast() through copy_to_user() and,
on -EFAULT, through rdma_leave_multicast() so leave cannot miss this join.
Do not leave if join itself failed: that path never published this address
on mc_list, and a leave-by-addr would destroy an earlier successful join.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98253</guid>
    </item>
  </channel>
</rss>
