Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write usr_len is read from a network-supplied message field (le16_to_cpu) and used to compute data_len = off - usr_len without validating that usr_len <= off. A malicious RDMA client can send usr_len > off causing an integer underflow, resulting in data_len wrapping to a huge size_t value which is then passed to the rdma_ev callback as a memory length, leading to out-of-bounds memory access. Fix by reading and validating usr_len <= off before rtrs_srv_get_ops_ids() in both process_read() and process_write(), ensuring the early return path acquires no reference and has no resource leak.

Published 24 Sep 2026Updated 25 Sep 20263 sources
CVSS 9.8

What happened

In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write usr_len is read from a network-supplied message field (le16_to_cpu) and used to compute data_len = off - usr_len without validating that usr_len <= off. A malicious RDMA client can send usr_len > off causing an integer underflow, resulting in data_len wrapping to a huge size_t value which is then passed to the rdma_ev callback as a memory length, leading to out-of-bounds memory access. Fix by reading and validating usr_len <= off before rtrs_srv_get_ops_ids() in both process_read() and process_write(), ensuring the early return path acquires no reference and has no resource leak.

Affected versions

Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 24ad03bfeda05fca04c56677e57fd3d6bc3e9978 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before c76e9123ab91a903396d26e6ab1b5caae5c6b149 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5 (git); before 6.12.111 (semver); before 6.18.53 (semver) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.