CVE-2026-93228svcrdma: Reject Write/Reply chunks with segcount 0
- 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: Reject Write/Reply chunks with segcount 0 A peer can send a Write or Reply chunk whose segcount field is zero. xdr_check_write_chunk() only rejects segcount > rc_maxpages, so zero passes the range check, and xdr_inline_decode(stream, 0) returns the current (non-NULL) cursor without advancing. The function returns true and pcl_alloc_write() then links a struct svc_rdma_chunk with ch_segcount == 0 onto rc_write_pcl or rc_reply_pcl. An earlier patch in this series made pcl_for_each_segment() safe for ch_segcount == 0, so this no longer drives the memory walk it used to. Rejecting the malformed frame at the decode boundary is still worthwhile as defense in depth: it keeps degenerate zero-segment chunks off the parsed chunk lists entirely, so any future consumer that walks ch_segments directly cannot observe one, and it makes the zero-floor easy to backport to trees where the macro change is more intrusive. RFC 8166 has no meaning for a Write/Reply chunk that describes no remote buffer, so no legitimate client is affected. xdr_check_reply_chunk() funnels Reply chunks through xdr_check_write_chunk() and inherits the same rejection. pcl_alloc_write() also links each chunk onto the parsed chunk list before filling its segment array. If a future change weakens the segcount-0 rejection, an incomplete chunk is visible to consumers during the fill loop. Reorder so that list_add_tail() follows the segment fill loop, ensuring only fully-populated chunks appear on the list.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 36 days later
· 36 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)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.
Affected products
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < ac730b8cbaeec6831116e1455d909ecbdcdcbd34
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 28c5a3a572f6cf81ac304459cfd515480995d62a
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < fe533ae1bed2ef2b3d54ee7ab410da1874ed3d4f
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < a798714b58041e88716db3bf8fb03ae13eecd54a
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 45dbdb2637b7fc5f1355b588780d2a7fb0516805
- affected 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 – < 9808eb7656666acc7291bae9ab6b987bd16e47e0
- affected 5.11
- unaffected < 5.11
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ac730b8cbaeec6831116e1455d909ecbdcdcbd34 (opens in a new tab)
- https://git.kernel.org/stable/c/28c5a3a572f6cf81ac304459cfd515480995d62a (opens in a new tab)
- https://git.kernel.org/stable/c/fe533ae1bed2ef2b3d54ee7ab410da1874ed3d4f (opens in a new tab)
- https://git.kernel.org/stable/c/a798714b58041e88716db3bf8fb03ae13eecd54a (opens in a new tab)
- https://git.kernel.org/stable/c/45dbdb2637b7fc5f1355b588780d2a7fb0516805 (opens in a new tab)
- https://git.kernel.org/stable/c/9808eb7656666acc7291bae9ab6b987bd16e47e0 (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-86233 (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-93228)Record last updated .