PoC Monitor
← All CVEs
CVE-2026-89530published 11 Sep 2026 19:44 UTCData: JSON · API

Linux

svcrdma: Reject inline replies that overflow the pull-up buffer

In the Linux kernel, the following vulnerability has been resolved: svcrdma: Reject inline replies that overflow the pull-up buffer An RPC-over-RDMA client can request a reply, such as an NFS READ payload, without providing a Write list or a Reply chunk to carry it. When such a reply needs more scatter/gather entries than the device's Send Queue supports, svc_rdma_pull_up_needed() selects pull-up and svc_rdma_pull_up_reply_msg() linearizes the whole reply into sctxt->sc_xprt_buf. That buffer is only sc_max_req_size bytes, while the reply on this path is bounded only by the client's request, so svc_rdma_xb_linearize() copies past the end of the buffer and corrupts adjacent slab memory. The oversized length is then stored in sc_sges[0].length and posted, so the device also reads beyond the mapped region. The SGE-exhaustion branch is the only pull-up path that can exceed the buffer: the threshold branch pulls up only replies smaller than RPCRDMA_PULLUP_THRESH, and replies that fit the device's SGE budget are sent directly without linearization. Make svc_rdma_pull_up_needed() report -E2BIG when the reply it would pull up cannot fit sc_max_req_size, and fail the request with ERR_CHUNK as RFC 8166 Section 4.5.3 directs rather than dropping the connection. The helper no longer answers a simple yes/no question: it now reports pull-up, no pull-up, or -E2BIG for a reply too large to linearize. Rename svc_rdma_pull_up_needed() to svc_rdma_check_pull_up() so its name no longer implies a boolean predicate.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.8critical · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= e248aa7be86e8179f20ac0931774ecd746f3f5bf, < b73011049dbe909f73fd9620d94ef1757d7af2eb
  • >= e248aa7be86e8179f20ac0931774ecd746f3f5bf, < 8068358f445a11296328ffa7c524701596814a17
  • >= e248aa7be86e8179f20ac0931774ecd746f3f5bf, < fcd91b9957462d398792201c239dffaeff1cc8b2
  • >= e248aa7be86e8179f20ac0931774ecd746f3f5bf, < 1949dd1576f7a8aa161b1330c6125df9d53046d5
  • >= e248aa7be86e8179f20ac0931774ecd746f3f5bf, < 8ec60eb51fae37cd3d334ff26e4a7d6fb21ff7cf
  • >= e248aa7be86e8179f20ac0931774ecd746f3f5bf, < 0fbe20dfe74b783d255bf389a6ea77aa25dc7860
  • 9b65b18f817d9ada2bf67351f24bdcce6789a0bb
  • d564356e1919d1178568c19af410cfc1a9076663
  • >= 4.19.22, < 4.20
  • >= 4.20.9, < 4.21

Fixed in b73011049dbe909f73fd9620d94ef1757d7af2eb, 8068358f445a11296328ffa7c524701596814a17, fcd91b9957462d398792201c239dffaeff1cc8b2, 1949dd1576f7a8aa161b1330c6125df9d53046d5, 8ec60eb51fae37cd3d334ff26e4a7d6fb21ff7cf, 0fbe20dfe74b783d255bf389a6ea77aa25dc7860, 4.20, 4.21

Linux Linux
  • 5.0

Fixed in 0, 6.1.191, 6.6.160, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to b73011049dbe909f73fd9620d94ef1757d7af2eb or 8068358f445a11296328ffa7c524701596814a17 or fcd91b9957462d398792201c239dffaeff1cc8b2 or 1949dd1576f7a8aa161b1330c6125df9d53046d5 or 8ec60eb51fae37cd3d334ff26e4a7d6fb21ff7cf or 0fbe20dfe74b783d255bf389a6ea77aa25dc7860 or 4.20 or 4.21 or later.

Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.