CVE-2026-53186: RDMA/srp: bound SRP_RSP sense copy by the received length
In the Linux kernel, the following vulnerability has been resolved:
RDMA/srp: bound SRPRSP sense copy by the received length
srpprocessrsp() copies sense data from rsp->data + respdatalen, where respdatalen is the full 32-bit value supplied by the SRP target and is never checked against the number of bytes actually received (wc->bytelen). The copy length is bounded to SCSISENSEBUFFERSIZE, so at most 96 bytes are copied, but the source offset is not bounded.
A malicious or compromised SRP target on the InfiniBand/RoCE fabric that the initiator has logged into can return an SRPRSP with SRPRSPFLAGSNSVALID set and a large respdatalen. The receive buffer is allocated at the target-chosen maxtiiulen, so the source of the sense copy lands past the bytes actually received; with respdatalen near 0xFFFFFFFF it is gigabytes past the buffer and the read faults.
Copy the sense data only if it has not been truncated, that is, only if the response header, the response data, and the sense region fit within the bytes actually received; otherwise drop the sense and log. The in-tree iSER and NVMe-RDMA receive paths already bound their parse by wc->bytelen; this brings ibsrp into line with them.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53186?
The severity of CVE-2026-53186 is rated as critical with a score of 9.1.
What impact does CVE-2026-53186 have on affected systems?
CVE-2026-53186 may allow unauthorized access to sensitive data due to improper handling of memory boundaries.
How do I fix CVE-2026-53186?
To fix CVE-2026-53186, update the Linux kernel to the latest version that includes the security patch.
What systems are affected by CVE-2026-53186?
CVE-2026-53186 affects the Linux kernel and the Microsoft azl3 kernel version 6.6.141.1-1.
When was CVE-2026-53186 published?
CVE-2026-53186 was published on June 25, 2026.