xprtrdma: Sanitize the reply credit grant after parsing
In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Sanitize the reply credit grant after parsing The out_norqst exit in rpcrdma_reply_handler() branches away before the credit clamp, so a reply that matches no pending request reaches out_post carrying the raw credit value parsed from the wire. rpcrdma_post_recvs() does not bound its @needed argument: the refill loop allocates and chains Receive WRs until the count is satisfied or allocation fails. A peer that sends a well-formed reply carrying an unknown XID and an inflated credit grant therefore drives rep allocation and Receive posting past re_max_requests on every such reply. Move the clamp to immediately after the credit field is parsed, ahead of the first branch that can reach out_post, so every later consumer sees a sanitized value. The cwnd update stays on the matched-request path.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.7% · 51th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
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.7%
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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
- 7.1affected
- d01d6670c169316115b26dfb3585a73dfe40b563 and later · before 7cf332b3d82d73ffceedca6b4a120be074172021affected · git
- d1b159356a3584943192712392fcb2439aafb8c1 and later · before 41634242140173eabbf54f899f9c70b5c685e786affected · git
- 17da9e0caa8615f6fc3b4022eadbd78a9aea1a2a and later · before 8be1bb378def94a5cb8f7527a191e476407118ecaffected · git
- e7ae0883c8c89b901226de43862184bf37054338 and later · before 469b22376ee73369711ecf2761bd122ef4195963affected · git
- 704f3f640f72db4d44ec5ce3db8d4e150c974bc7 and later · before 33db78b1b24fc6a464ae08aa4d2538c5f883eb5eaffected · git
- 704f3f640f72db4d44ec5ce3db8d4e150c974bc7 and later · before c3a628aab2dc8f5fd7bff86ceaeae64de590e60aaffected · git
- before 7.1not affected · semver
- 7.1.5 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| 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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 33db78b1b24fc6a464ae08aa4d2538c5f883eb5e | Vendor (CNA) |
| Linux Linux | 41634242140173eabbf54f899f9c70b5c685e786 | Vendor (CNA) |
| Linux Linux | 469b22376ee73369711ecf2761bd122ef4195963 | Vendor (CNA) |
| Linux Linux | 7cf332b3d82d73ffceedca6b4a120be074172021 | Vendor (CNA) |
| Linux Linux | 8be1bb378def94a5cb8f7527a191e476407118ec | Vendor (CNA) |
| Linux Linux | c3a628aab2dc8f5fd7bff86ceaeae64de590e60a | Vendor (CNA) |
| debian:linux | 7.1.5-1 · Debian:14 | 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/33db78b1b24fc6a464ae08aa4d2538c5f883eb5e
- git.kernel.org/stable/c/41634242140173eabbf54f899f9c70b5c685e786
- git.kernel.org/stable/c/469b22376ee73369711ecf2761bd122ef4195963
- git.kernel.org/stable/c/7cf332b3d82d73ffceedca6b4a120be074172021
- git.kernel.org/stable/c/8be1bb378def94a5cb8f7527a191e476407118ec
- git.kernel.org/stable/c/c3a628aab2dc8f5fd7bff86ceaeae64de590e60a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.