Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-72465, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.68% · top 47% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected d01d6670c169316115b26dfb3585a73dfe40b563 – < 7cf332b3d82d73ffceedca6b4a120be074172021
    • affected d1b159356a3584943192712392fcb2439aafb8c1 – < 41634242140173eabbf54f899f9c70b5c685e786
    • affected 17da9e0caa8615f6fc3b4022eadbd78a9aea1a2a – < 8be1bb378def94a5cb8f7527a191e476407118ec
    • affected e7ae0883c8c89b901226de43862184bf37054338 – < 469b22376ee73369711ecf2761bd122ef4195963
    • affected 704f3f640f72db4d44ec5ce3db8d4e150c974bc7 – < 33db78b1b24fc6a464ae08aa4d2538c5f883eb5e
    • affected 704f3f640f72db4d44ec5ce3db8d4e150c974bc7 – < c3a628aab2dc8f5fd7bff86ceaeae64de590e60a
  • Linux · Linux

    • affected 7.1
    • unaffected < 7.1
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72465 badge
[![CVE-2026-72465](https://cveledger.app/badge/CVE-2026-72465.svg)](https://cveledger.app/cve/CVE-2026-72465)

Record last updated .