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-72467

xprtrdma: Check frwr_wp_create() during connect

Description

In the Linux kernel, the following vulnerability has been resolved: xprtrdma: Check frwr_wp_create() during connect frwr_wp_create() creates the singleton Memory Region used to encode padding for Write chunks whose payload length is not XDR-aligned. Its failure paths return a negative errno and leave ep->re_write_pad_mr set to NULL. rpcrdma_xprt_connect() currently ignores that return value. If frwr_wp_create() fails after the rest of the connection setup succeeds, xprt_rdma_connect_worker() treats the connection attempt as successful and sets XPRT_CONNECTED. A later NFS/RDMA read with a non-4-byte-aligned receive page length reaches rpcrdma_encode_write_list(), passes the NULL write-pad MR to encode_rdma_segment(), and dereferences it. This is locally triggerable on an NFS/RDMA client after a connect or reconnect hits a local MR allocation, DMA-map, MR-map, or post-send failure; a remote peer alone cannot force the local MR setup failure. Check the return value and fail the connect as -ENOTCONN, matching the adjacent setup failures. This keeps XPRT_CONNECTED clear and lets the normal reconnect path retry.

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (11 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 21037b8c2258ec40de3b31be9ced43ceb3b784f7 – < 3b252fe1778b2cdd68283146455929801bc2abd7
    • affected 21037b8c2258ec40de3b31be9ced43ceb3b784f7 – < dd798b76a3481e392820c3ae86ed4592858c6b0f
    • affected 21037b8c2258ec40de3b31be9ced43ceb3b784f7 – < 6b7be4f3feae322f1c2c40a3bdc99db93574a49e
    • affected 21037b8c2258ec40de3b31be9ced43ceb3b784f7 – < 7471e66373a4444a57ef2192f8c4081202c54f45
    • affected 21037b8c2258ec40de3b31be9ced43ceb3b784f7 – < ef3b79edf14b6bfb0d21a26ccb0463f9cf82c6a9
    • affected 21037b8c2258ec40de3b31be9ced43ceb3b784f7 – < 0f13fc7c7d2e0427517e63c739277a4cd338b0c5
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • 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-72467 badge
[![CVE-2026-72467](https://cveledger.app/badge/CVE-2026-72467.svg)](https://cveledger.app/cve/CVE-2026-72467)

Record last updated .