CVE-2026-72466xprtrdma: Fix bcall rep leak and unbounded peek
- 9.8CriticalCVSS base score
- 0.73%Exploitation in 30 daysEPSS · top 45% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Fix bcall rep leak and unbounded peek rpcrdma_is_bcall() decodes a reply'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. First, the speculative peek p = xdr_inline_decode(xdr, 0); /* five p++ reads follow */ asks xdr_inline_decode() for zero bytes, which returns xdr->p without consulting xdr->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. Second, after the post-peek p = xdr_inline_decode(xdr, 3 * sizeof(*p)); if (unlikely(!p)) return true; 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: rpcrdma_reply_handler() if (rpcrdma_is_bcall(r_xprt, rep)) return; /* bare return, skips out_post */ ... out_post: rpcrdma_post_recvs(r_xprt, credits + ...); 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 nothing, so its slot is reclaimed only when a later forward-channel reply reaches out_post and rpcrdma_post_recvs() allocates a fresh rep to backfill; absent that traffic the Receive queue drains and the peer's Sends draw RNR NAKs. Fix by consulting xdr->end after the zero-length peek so the five __be32 reads cannot run unless 20 bytes of wire payload remain. A byte-precise comparison against xdr->end is required because a non-4-aligned receive rounds the stream's word count up past the true payload. Also return false from the short-header arm so the reply falls through the normal out_norqst cleanup chain (rpcrdma_rep_put() plus rpcrdma_post_recvs()).
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.73% · top 45% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.
Affected products
- affected 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 – < 0cee8f9c3b14bd6dee9c4310090a7f45b89b834f
- affected 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 – < 7afc2f8d2fd9394724df9eaf22ce7a71029a5fba
- affected 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 – < 88b5346284a184a6b7d019912232a571d672d3e3
- affected 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 – < 07aa506436be7634e381e1e1f6d0efa9efc81ecc
- affected 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 – < d7a2870dde3bb09d51d6b9c877642996ad6b92dd
- affected 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 – < 118a16a18c59f7ad8084b2d13988839b669fca10
- affected 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 – < c7653d5cebc8492c77ec0415b5e9c0fb3e644bc6
- affected 4.14
- unaffected < 4.14
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/0cee8f9c3b14bd6dee9c4310090a7f45b89b834f (opens in a new tab)
- https://git.kernel.org/stable/c/7afc2f8d2fd9394724df9eaf22ce7a71029a5fba (opens in a new tab)
- https://git.kernel.org/stable/c/88b5346284a184a6b7d019912232a571d672d3e3 (opens in a new tab)
- https://git.kernel.org/stable/c/07aa506436be7634e381e1e1f6d0efa9efc81ecc (opens in a new tab)
- https://git.kernel.org/stable/c/d7a2870dde3bb09d51d6b9c877642996ad6b92dd (opens in a new tab)
- https://git.kernel.org/stable/c/118a16a18c59f7ad8084b2d13988839b669fca10 (opens in a new tab)
- https://git.kernel.org/stable/c/c7653d5cebc8492c77ec0415b5e9c0fb3e644bc6 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59365 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72466)Record last updated .