PT-2026-90249 · Linux · Linux

CVE-2026-89533

·

Published

2026-09-11

·

Updated

2026-09-11

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
svcrdma: Fix offset arithmetic in read chunk range
svc rdma read chunk range() walks a Read chunk's segment list to build a sub-range starting at byte offset and spanning length bytes for a Position-Zero or Call chunk. Two arithmetic defects in the per-segment loop produce wrong DMA lengths and a u32 underflow:
pcl for each segment(segment, chunk) { if (offset > segment->rs length) { offset -= segment->rs length; continue; }
  dummy.rs handle = segment->rs handle;
  dummy.rs length = min t(u32, length,
              segment->rs length) - offset;
  dummy.rs offset = segment->rs offset + offset;
First, the skip predicate uses '>' instead of '>='. When offset equals the segment's full rs length, the segment is fully consumed and should be skipped, but the loop falls through into the body. The resulting dummy.rs length is min t(u32, length, rs length) - rs length, which underflows to a near-UINT MAX u32 when length is smaller than rs length, or is zero otherwise.
Second, the length formula subtracts offset from the min t() result rather than from segment->rs length before the cap. For offset > 0 the segment's residual is rs length - offset, not rs length, so the cap must be applied to the residual. With the current bracketing, whenever length is smaller than rs length - offset the per-segment length becomes length - offset instead of length, silently dropping offset bytes from the rebuilt chunk. Combined with the boundary case above it also enables the u32 underflow path, which propagates a huge nr bvec into svc rdma build read segment() and a multi-MiB kmalloc array node() in svc rdma get rw ctxt().
Additionally, svc rdma read call chunk() can invoke this function with length == 0 when the last Read chunk ends exactly at the end of the Call chunk. With the corrected >= predicate, every segment is skipped and the function returns the initial -EINVAL, rejecting a valid request. Return success immediately when length is zero. Also break out of the loop once length is fully consumed to avoid passing zero-length segments to svc rdma build read segment().
Fix by using '>=' so a fully-consumed segment is skipped, by moving '- offset' inside min t() so the cap is applied to the segment's residual length, by returning success for zero-length requests, and by stopping iteration when the requested range has been consumed.
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

CVE-2026-89533

Affected Products

Linux