CVE-2026-72466: xprtrdma: Fix bcall rep leak and unbounded peek
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.73% (FIRST EPSS); higher than 55% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 07aa506436be7634e381e1e1f6d0efa9efc81ecc, 0cee8f9c3b14bd6dee9c4310090a7f45b89b834f, 118a16a18c59f7ad8084b2d13988839b669fca10.
Low priority for now. Upgrade to Linux Linux 07aa506436be7634e381e1e1f6d0efa9efc81ecc, 0cee8f9c3b14bd6dee9c4310090a7f45b89b834f, 118a16a18c59f7ad8084b2d13988839b669fca10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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()).
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- —
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.14affected
- 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 and later · before 0cee8f9c3b14bd6dee9c4310090a7f45b89b834faffected · git
- 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 and later · before 7afc2f8d2fd9394724df9eaf22ce7a71029a5fbaaffected · git
- 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 and later · before 88b5346284a184a6b7d019912232a571d672d3e3affected · git
- 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 and later · before 07aa506436be7634e381e1e1f6d0efa9efc81eccaffected · git
- 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 and later · before d7a2870dde3bb09d51d6b9c877642996ad6b92ddaffected · git
- 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 and later · before 118a16a18c59f7ad8084b2d13988839b669fca10affected · git
- 41c8f70f5a3db7e06179186b6525fd9ee1d7d314 and later · before c7653d5cebc8492c77ec0415b5e9c0fb3e644bc6affected · git
- before 4.14not affected · semver
- 5.15.212 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72463Aug 15, 2026 · xfrm: Fix dev use-after-free in xfrm async resumption39Monitor
- ← EarlierCVE-2026-72464Aug 15, 2026 · xprtrdma: Repost Receive buffers for malformed replies30Monitor
- Later →CVE-2026-72469Aug 15, 2026 · xprtrdma: Fix ep kref imbalance on ADDR_CHANGE35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 07aa506436be7634e381e1e1f6d0efa9efc81ecc | Vendor (CNA) |
| Linux Linux | 0cee8f9c3b14bd6dee9c4310090a7f45b89b834f | Vendor (CNA) |
| Linux Linux | 118a16a18c59f7ad8084b2d13988839b669fca10 | Vendor (CNA) |
| Linux Linux | 7afc2f8d2fd9394724df9eaf22ce7a71029a5fba | Vendor (CNA) |
| Linux Linux | 88b5346284a184a6b7d019912232a571d672d3e3 | Vendor (CNA) |
| Linux Linux | c7653d5cebc8492c77ec0415b5e9c0fb3e644bc6 | Vendor (CNA) |
| Linux Linux | d7a2870dde3bb09d51d6b9c877642996ad6b92dd | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/0cee8f9c3b14bd6dee9c4310090a7f45b89b834f
- git.kernel.org/stable/c/118a16a18c59f7ad8084b2d13988839b669fca10
- git.kernel.org/stable/c/7afc2f8d2fd9394724df9eaf22ce7a71029a5fba
- git.kernel.org/stable/c/88b5346284a184a6b7d019912232a571d672d3e3
- git.kernel.org/stable/c/c7653d5cebc8492c77ec0415b5e9c0fb3e644bc6
- git.kernel.org/stable/c/d7a2870dde3bb09d51d6b9c877642996ad6b92dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.