CVE-2026-89530
CVE CVE-2026-89530EUVD EUVD-2026-76436Published 2026-09-11T19:44:10.000ZLast changed 2026-09-13T06:30:27.000ZCVSS 9.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux e248aa7be86e8179f20ac0931774ecd746f3f5bf <8ec60eb51fae37cd3d334ff26e4a7d6fb21ff7cf; patch: 0; d564356e1919d1178568c19af410cfc1a9076663; patch: 7.2.4; patch: 6.18.50; 4.19.22 <4.20; 9b65b18f817d9ada2bf67351f24bdcce6789a0bb; patch: 7.3-rc1; e248aa7be86e8179f20ac0931774ecd746f3f5bf <fcd91b9957462d398792201c239dffaeff1cc8b2; patch: 6.12.109; 5.0; e248aa7be86e8179f20ac0931774ecd746f3f5bf <0fbe20dfe74b783d255bf389a6ea77aa25dc7860; e248aa7be86e8179f20ac0931774ecd746f3f5bf <1949dd1576f7a8aa161b1330c6125df9d53046d5; 4.20.9 <4.21
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.