CVE-2026-93228

svcrdma: Reject Write/Reply chunks with segcount 0

  • Critical 9.1

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.

Key facts

Published
24 Sep 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.501% likely to be exploited in the next 30 days, higher than 43.532% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 9.1CVSS 3.1, Criticalfrom the CNA (Linux)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 up to but excluding ac730b8cbaeec6831116e1455d909ecbdcdcbd34 (affected)
  • 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 up to but excluding 28c5a3a572f6cf81ac304459cfd515480995d62a (affected)
  • 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 up to but excluding fe533ae1bed2ef2b3d54ee7ab410da1874ed3d4f (affected)
  • 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 up to but excluding a798714b58041e88716db3bf8fb03ae13eecd54a (affected)
  • 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 up to but excluding 45dbdb2637b7fc5f1355b588780d2a7fb0516805 (affected)
  • 78147ca8b4a9b6cf0e597ddd6bf17959e08376c2 up to but excluding 9808eb7656666acc7291bae9ab6b987bd16e47e0 (affected)
LinuxLinux
  • Default status: affected
  • 5.11 (affected)
  • 0 up to but excluding 5.11 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.50 up to and including 6.18.* (unaffected)
  • 7.2.4 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References