CVE-2026-89532svcrdma: Fix pcl_for_each_segment for empty chunks
- 9.1CriticalCVSS base score
- 0.50%Exploitation in 30 daysEPSS · top 56% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: svcrdma: Fix pcl_for_each_segment for empty chunks When a parsed chunk list contains a chunk whose ch_segcount is zero, pcl_for_each_segment computes its inclusive upper bound as &chunk->ch_segments[ch_segcount - 1]. ch_segcount is u32, so the subtraction wraps to 0xFFFFFFFF and the bound lands far past the ch_segments flex array. The loop body then walks unrelated memory at sizeof(struct svc_rdma_segment) stride until it faults. A zero-segcount chunk is reachable from the wire: xdr_check_write_chunk() only rejects segcount values greater than rc_maxpages, and pcl_alloc_write() links a freshly allocated chunk onto rc_write_pcl/rc_reply_pcl before its segment-fill loop runs, so a Write or Reply chunk advertising zero segments leaves ch_segcount == 0 on the list. When the transport has negotiated Send-With-Invalidate, svc_rdma_get_inv_rkey() iterates all four PCLs with pcl_for_each_segment and dereferences segment->rs_handle on each iteration, turning the underflow into an out-of-bounds read and a general protection fault. xdr_check_write_list / xdr_check_reply_chunk pcl_alloc_write() chunk = pcl_alloc_chunk(...) /* ch_segcount = 0 */ list_add_tail(&chunk->ch_list, &pcl->cl_chunks) /* fill loop iterates zero times for wire segcount 0 */ svc_rdma_get_inv_rkey() pcl_for_each_chunk(rc_write_pcl) pcl_for_each_segment(segment, chunk) pos <= &ch_segments[0u - 1u] /* 0xFFFFFFFF */ segment->rs_handle /* OOB read -> GPF */ Fix by switching the macro to a half-open upper bound that uses ch_segcount directly. For ch_segcount == 0 the loop start equals the loop end and the body is skipped; for ch_segcount > 0 the iteration range is unchanged. All six existing call sites in net/sunrpc/xprtrdma/svc_rdma_recvfrom.c and net/sunrpc/xprtrdma/svc_rdma_rw.c remain correct under the new bound, so no caller changes are needed.
Timeline
ID reserved
By Linux
Published
- 38 days later
· 38 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVDNVD · Received | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.50% · top 56% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.
Affected products
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 1e2e3481e39103a386b86be1c33eaef97cbdf16e
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 3a78b841879c2a3243f74edc514236fb2907167f
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 06d0390c37fa6714624af771bd72bbf1a7ed9bb1
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 9c5a03c3dc505c0295339b0a1b9e4fe36447e482
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < a1c954ca4977a4e6ec73ef92fe48073ec54f9fc8
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 6d33a7e6bf6c6b293a266a617201285a1ad32c56
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < b7713a784c59515d0aba558c8f5df6a0164dd3a9
- affected 5.11
- unaffected < 5.11
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 6.6.*
- unaffected 6.12.109 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/1e2e3481e39103a386b86be1c33eaef97cbdf16e (opens in a new tab)
- https://git.kernel.org/stable/c/3a78b841879c2a3243f74edc514236fb2907167f (opens in a new tab)
- https://git.kernel.org/stable/c/06d0390c37fa6714624af771bd72bbf1a7ed9bb1 (opens in a new tab)
- https://git.kernel.org/stable/c/9c5a03c3dc505c0295339b0a1b9e4fe36447e482 (opens in a new tab)
- https://git.kernel.org/stable/c/a1c954ca4977a4e6ec73ef92fe48073ec54f9fc8 (opens in a new tab)
- https://git.kernel.org/stable/c/6d33a7e6bf6c6b293a266a617201285a1ad32c56 (opens in a new tab)
- https://git.kernel.org/stable/c/b7713a784c59515d0aba558c8f5df6a0164dd3a9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76438 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89532)Record last updated .