<?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>Wed, 30 Sep 2026 03:57:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72466 — xprtrdma: Fix bcall rep leak and unbounded peek</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72466</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;xprtrdma: Fix bcall rep leak and unbounded peek&lt;/p&gt;
&lt;p&gt;rpcrdma_is_bcall() decodes a reply&amp;#39;s first words to decide whether
the frame is a backchannel call. Two issues in that decode path
let a short or malformed reply leak the receive buffer and drain
the Receive queue.&lt;/p&gt;
&lt;p&gt;First, the speculative peek&lt;/p&gt;
&lt;p&gt;p = xdr_inline_decode(xdr, 0);
    /* five p++ reads follow */&lt;/p&gt;
&lt;p&gt;asks xdr_inline_decode() for zero bytes, which returns xdr-&amp;gt;p
without consulting xdr-&amp;gt;end. The five subsequent __be32 reads can
then walk up to 20 bytes past the wire payload into stale regbuf
contents and misclassify the reply as a backchannel call.&lt;/p&gt;
&lt;p&gt;Second, after the post-peek&lt;/p&gt;
&lt;p&gt;p = xdr_inline_decode(xdr, 3 * sizeof(*p));
    if (unlikely(!p))
            return true;&lt;/p&gt;
&lt;p&gt;the short-header arm returns true without calling
rpcrdma_bc_receive_call(). The contract with the caller is that a
true return transfers ownership of rep to the backchannel path:&lt;/p&gt;
&lt;p&gt;rpcrdma_reply_handler()
      if (rpcrdma_is_bcall(r_xprt, rep))
              return;        /* bare return, skips out_post */
      ...
    out_post:
      rpcrdma_post_recvs(r_xprt, credits + ...);&lt;/p&gt;
&lt;p&gt;Because rpcrdma_bc_receive_call() never ran, no one took rep, but
rpcrdma_reply_handler still bare-returns past rpcrdma_rep_put()
and rpcrdma_post_recvs(). The rep, with its persistently
DMA-mapped receive buffer, is orphaned on rb_all_reps and freed
only at transport teardown. This completion reposts n…&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;xprtrdma: Fix bcall rep leak and unbounded peek&lt;/p&gt;
&lt;p&gt;rpcrdma_is_bcall() decodes a reply&amp;#39;s first words to decide whether
the frame is a backchannel call. Two issues in that decode path
let a short or malformed reply leak the receive buffer and drain
the Receive queue.&lt;/p&gt;
&lt;p&gt;First, the speculative peek&lt;/p&gt;
&lt;p&gt;p = xdr_inline_decode(xdr, 0);
    /* five p++ reads follow */&lt;/p&gt;
&lt;p&gt;asks xdr_inline_decode() for zero bytes, which returns xdr-&amp;gt;p
without consulting xdr-&amp;gt;end. The five subsequent __be32 reads can
then walk up to 20 bytes past the wire payload into stale regbuf
contents and misclassify the reply as a backchannel call.&lt;/p&gt;
&lt;p&gt;Second, after the post-peek&lt;/p&gt;
&lt;p&gt;p = xdr_inline_decode(xdr, 3 * sizeof(*p));
    if (unlikely(!p))
            return true;&lt;/p&gt;
&lt;p&gt;the short-header arm returns true without calling
rpcrdma_bc_receive_call(). The contract with the caller is that a
true return transfers ownership of rep to the backchannel path:&lt;/p&gt;
&lt;p&gt;rpcrdma_reply_handler()
      if (rpcrdma_is_bcall(r_xprt, rep))
              return;        /* bare return, skips out_post */
      ...
    out_post:
      rpcrdma_post_recvs(r_xprt, credits + ...);&lt;/p&gt;
&lt;p&gt;Because rpcrdma_bc_receive_call() never ran, no one took rep, but
rpcrdma_reply_handler still bare-returns past rpcrdma_rep_put()
and rpcrdma_post_recvs(). The rep, with its persistently
DMA-mapped receive buffer, is orphaned on rb_all_reps and freed
only at transport teardown. This completion reposts n…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72466</guid>
    </item>
  </channel>
</rss>
