CVE-2026-72464: xprtrdma: Repost Receive buffers for malformed replies
Noroxi assessment
Priority: Monitor (action score 30/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.67% (FIRST EPSS); higher than 52.4% 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 007b4da2f38dcc16a13265416f4ca9f179bab610, 19fae02b272ee4bcdfb5db57f402d28f1697167a, 4322fd9645ee769ad29ce5caea74a1cd9b17269d.
Low priority for now. Upgrade to Linux Linux 007b4da2f38dcc16a13265416f4ca9f179bab610, 19fae02b272ee4bcdfb5db57f402d28f1697167a, 4322fd9645ee769ad29ce5caea74a1cd9b17269d 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: Repost Receive buffers for malformed replies rpcrdma_wc_receive() decrements the transport's Receive count for every completion before it dispatches a successful Receive to rpcrdma_reply_handler(). The handler must post a replacement Receive WR before returning unless ownership of the rep has moved elsewhere, as on the backchannel path. Commit 2ae50ad68cd7 ("xprtrdma: Close window between waking RPC senders and posting Receives") moved the Receive refill out of rpcrdma_wc_receive(), where it had run ahead of every reply, into rpcrdma_reply_handler() so that the responder's credit grant could be parsed before reposting. The bad-version and short-reply exits never reach that refill: they recycle the rep and return without calling rpcrdma_post_recvs(). A remote peer can therefore drain the client's posted Receive queue by sending a sustained stream of replies that are shorter than the fixed transport header or that carry an unrecognized RPC/RDMA version. Each such reply consumes one posted Receive without replacing it. Once the queue empties, the peer's next Send finds no posted Receive and the transport stalls until reconnect. Route both malformed-reply exits through the shared repost tail after recycling the rep, refilling against buf->rb_credits, the most recent accepted credit grant. Neither exit updates the congestion window, so RPCs admitted under the previous grant remain in flight awaiting replies. A smaller refill target would let a stream of malformed replies ratchet the posted Receive count down to the batch floor while the congestion window still admits rb_credits RPCs; a burst of valid replies to those RPCs could then overrun the posted Receives, and because the client connects with rnr_retry_count of zero, a single RNR NAK terminates the connection. Refilling against rb_credits also restores the target that applied to malformed replies before commit 2ae50ad68cd7 ("xprtrdma: Close window between waking RPC senders and posting Receives") when rpcrdma_post_recvs() computed it from rb_credits internally. rb_credits is at least one from connection establishment onward, so the repost path always keeps Receives posted.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- 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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 3791c5982ba1eebf2900ee7ca7b9a89619c26d54, 5.5affected
- 2ae50ad68cd79224198b525f7bd645c9da98b6ff and later · before ef6fb8a5c521f1a07f85202d13e8f2898f247362affected · git
- 2ae50ad68cd79224198b525f7bd645c9da98b6ff and later · before 4322fd9645ee769ad29ce5caea74a1cd9b17269daffected · git
- 2ae50ad68cd79224198b525f7bd645c9da98b6ff and later · before 19fae02b272ee4bcdfb5db57f402d28f1697167aaffected · git
- 2ae50ad68cd79224198b525f7bd645c9da98b6ff and later · before 007b4da2f38dcc16a13265416f4ca9f179bab610affected · git
- 2ae50ad68cd79224198b525f7bd645c9da98b6ff and later · before d7c531ab477ae94fd03771d707fd29c787408039affected · git
- 2ae50ad68cd79224198b525f7bd645c9da98b6ff and later · before abc011ddaf1617e3e82d8a1e87daa7ddbfb9bac5affected · git
- 5.4.13 and later · before 5.5affected · semver
- before 5.5not affected · semver
- 6.1.178 and later · up to and including 6.1.*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-72454Aug 15, 2026 · i3c: mipi-i3c-hci: Fix race in i3c_hci_addr_to_dev()31Monitor
- ← EarlierCVE-2026-72463Aug 15, 2026 · xfrm: Fix dev use-after-free in xfrm async resumption39Monitor
- Later →CVE-2026-72466Aug 15, 2026 · xprtrdma: Fix bcall rep leak and unbounded peek39Monitor
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 | 007b4da2f38dcc16a13265416f4ca9f179bab610 | Vendor (CNA) |
| Linux Linux | 19fae02b272ee4bcdfb5db57f402d28f1697167a | Vendor (CNA) |
| Linux Linux | 4322fd9645ee769ad29ce5caea74a1cd9b17269d | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | abc011ddaf1617e3e82d8a1e87daa7ddbfb9bac5 | Vendor (CNA) |
| Linux Linux | d7c531ab477ae94fd03771d707fd29c787408039 | Vendor (CNA) |
| Linux Linux | ef6fb8a5c521f1a07f85202d13e8f2898f247362 | 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).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/19fae02b272ee4bcdfb5db57f402d28f1697167a
- git.kernel.org/stable/c/4322fd9645ee769ad29ce5caea74a1cd9b17269d
- git.kernel.org/stable/c/abc011ddaf1617e3e82d8a1e87daa7ddbfb9bac5
- git.kernel.org/stable/c/d7c531ab477ae94fd03771d707fd29c787408039
- git.kernel.org/stable/c/ef6fb8a5c521f1a07f85202d13e8f2898f247362
Vendor advisories and official records. Exploit/PoC links are deliberately left out.