# CVE-2026-72465: xprtrdma: Sanitize the reply credit grant after parsing

> A remote attacker can cause a denial of service in the Linux kernel by sending crafted RDMA replies with inflated credit grants, exhausting resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-72465, GHSA-qhx3-pwwp-v2cp, UBUNTU-CVE-2026-72465

## What is CVE-2026-72465?

CVE-2026-72465 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-72465?


## How do I fix CVE-2026-72465?

Apply the vendor's patch.

## Is CVE-2026-72465 being exploited?

There is no known exploitation of CVE-2026-72465 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72465 and fix it if it is affected.

What it is: CVE-2026-72465 is a high-severity denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72465 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72465/ (Markdown: https://insights.sbomify.com/CVE-2026-72465/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72465
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72465
- OSV: https://osv.dev/vulnerability/CVE-2026-72465

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72465/
Summaries are generated and may contain mistakes; the official description above is the record.