<?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>Mon, 28 Sep 2026 09:29:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89798 — rpcrdma: arm rn_done before publishing the notification</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89798</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;rpcrdma: arm rn_done before publishing the notification&lt;/p&gt;
&lt;p&gt;rpcrdma_rn_register() inserts @rn into rd_xa with xa_alloc() before
storing the caller&amp;#39;s callback in rn-&amp;gt;rn_done. The xarray makes @rn
reachable to rpcrdma_remove_one(), which walks rd_xa and invokes
rn-&amp;gt;rn_done(rn) for every registered notification. A device removal
that races a fresh registration can therefore observe @rn with
rn_done still NULL, because the notification objects are zero
allocated by their owners, and call through a NULL function pointer.&lt;/p&gt;
&lt;p&gt;Store rn-&amp;gt;rn_done before xa_alloc() publishes @rn. The xarray&amp;#39;s
store-side and load-side ordering then guarantees that any CPU which
finds @rn in rd_xa also observes the armed callback.&lt;/p&gt;
&lt;p&gt;rpcrdma_rn_unregister() treats a non-NULL rn_done as the sentinel
for a completed registration, so the early store must not survive a
failed registration. Clear rn_done again when xa_alloc() fails.
Were it left set, the failed-accept cleanup path would call
rpcrdma_rn_unregister() on an @rn that was never inserted, erasing
an unrelated rd_xa slot and underflowing rd_kref.&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;rpcrdma: arm rn_done before publishing the notification&lt;/p&gt;
&lt;p&gt;rpcrdma_rn_register() inserts @rn into rd_xa with xa_alloc() before
storing the caller&amp;#39;s callback in rn-&amp;gt;rn_done. The xarray makes @rn
reachable to rpcrdma_remove_one(), which walks rd_xa and invokes
rn-&amp;gt;rn_done(rn) for every registered notification. A device removal
that races a fresh registration can therefore observe @rn with
rn_done still NULL, because the notification objects are zero
allocated by their owners, and call through a NULL function pointer.&lt;/p&gt;
&lt;p&gt;Store rn-&amp;gt;rn_done before xa_alloc() publishes @rn. The xarray&amp;#39;s
store-side and load-side ordering then guarantees that any CPU which
finds @rn in rd_xa also observes the armed callback.&lt;/p&gt;
&lt;p&gt;rpcrdma_rn_unregister() treats a non-NULL rn_done as the sentinel
for a completed registration, so the early store must not survive a
failed registration. Clear rn_done again when xa_alloc() fails.
Were it left set, the failed-accept cleanup path would call
rpcrdma_rn_unregister() on an @rn that was never inserted, erasing
an unrelated rd_xa slot and underflowing rd_kref.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89798</guid>
    </item>
  </channel>
</rss>
