Linux Kernel up to 7.1.4 xprtrdma rpcrdma_reply_handler needed allocation of resources

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.48+ |
Summary
A vulnerability identified as very critical has been detected in Linux Kernel up to 7.1.4. This issue affects the function rpcrdma_reply_handler of the component xprtrdma. The manipulation of the argument needed leads to allocation of resources.
This vulnerability is listed as CVE-2026-72465. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 7.1.4. This issue affects the function rpcrdma_reply_handler of the component xprtrdma. The manipulation of the argument needed with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-72465 since 08/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/15/2026). The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch 7cf332b3d82d73ffceedca6b4a120be074172021/41634242140173eabbf54f899f9c70b5c685e786/8be1bb378def94a5cb8f7527a191e476407118ec/469b22376ee73369711ecf2761bd122ef4195963/33db78b1b24fc6a464ae08aa4d2538c5f883eb5e/c3a628aab2dc8f5fd7bff86ceaeae64de590e60a is able to eliminate this problem.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.5
VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 7.1.5/7.2-rc1
Patch: 7cf332b3d82d73ffceedca6b4a120be074172021/41634242140173eabbf54f899f9c70b5c685e786/8be1bb378def94a5cb8f7527a191e476407118ec/469b22376ee73369711ecf2761bd122ef4195963/33db78b1b24fc6a464ae08aa4d2538c5f883eb5e/c3a628aab2dc8f5fd7bff86ceaeae64de590e60a
Timeline
08/09/2026 CVE reserved08/15/2026 Advisory disclosed
08/15/2026 VulDB entry created
08/15/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-72465 (🔒)
GCVE (CVE): GCVE-0-2026-72465
GCVE (VulDB): GCVE-100-391043
Entry
Created: 08/15/2026 17:14Changes: 08/15/2026 17:14 (60)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.