svcrdma: Validate Read chunk positions before reconstruction
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d96962e6d0e281bab6a48e83b42f5dce6eb28bf4 · < 3779b7b9e7d1c8ba4738f9d327de3b0288cefe9b| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
svcrdma: Validate Read chunk positions before reconstruction
The RPC/RDMA Read chunk position field is supplied by the remote client and stored verbatim in the parsed chunk list. xdr_count_read_segments() checks only 4-byte alignment; it never compares the position against the received inline body length.
In the single-chunk path, svc_rdma_read_complete_one() splits the head and tail kvecs at ch_position. A position past the inline body underflows the tail length, exposing adjacent slab memory to the upper XDR decoder.
In the multi-chunk path, svc_rdma_read_multiple_chunks() computes gap lengths between chunks as unsigned subtractions from ch_position. Overlapping Read chunks cause these subtractions to underflow. A final position past the inline body likewise underflows the trailing gap length. svc_rdma_copy_inline_range() then copies past the receive buffer into request pages that are returned to the client through the Reply channel.
Bound inline-range copies in svc_rdma_copy_inline_range() against the decoded inline RPC body saved in rc_saved_arg. Reject a single Read chunk positioned beyond that body, and reject multi-chunk lists where accumulated read bytes exceed the next chunk's position. Apply the same position and overlap checks in the call-chunk interleaving path.
From the CVE record · Linux
The Linux kernel's RPC/RDMA service does not adequately validate client-supplied Read chunk positions against the inline RPC body. A remote client can use out-of-range or overlapping chunks to trigger out-of-bounds reads; in the multi-chunk path, adjacent memory can be copied into pages returned through the Reply channel. The input does not specify whether authentication or user interaction is required.
Engineers running Linux kernels with the RPC/RDMA service should check their vendor's advisory for affected versions; none are specified here.