CVE-2026-53186 RDMA/srp: bound SRP_RSP sense copy by the received length
A malicious SRP target can cause a kernel crash by triggering an out-of-bounds read in the Linux kernel's RDMA/SRP driver via crafted response lengths.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-53186?
CVE-2026-53186 is a critical memory corruption vulnerability in Linux kernel, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
RDMA/srp: bound SRP_RSP sense copy by the received length
srp_process_rsp() copies sense data from rsp->data + resp_data_len, where resp_data_len is the full 32-bit value supplied by the SRP target and is never checked against the number of bytes actually received (wc->byte_len). The copy length is bounded to SCSI_SENSE_BUFFERSIZE, 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 SRP_RSP with SRP_RSP_FLAG_SNSVALID set and a large resp_data_len. The receive buffer is allocated at the target-chosen max_ti_iu_len, so the source of the sense copy lands past the bytes actually received; with resp_data_len 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->byte_len; this brings ib_srp into line with them.
Weakness: CWE-125
Which versions are affected by CVE-2026-53186?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2026-53186?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-53186 being exploited?
There is no known exploitation of CVE-2026-53186 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as AZL-90434, BELL-CVE-2026-53186, DEBIAN-CVE-2026-53186, GHSA-fxr4-2qh7-r53g, ROOT-OS-DEBIAN-11-CVE-2026-53186, ROOT-OS-DEBIAN-12-CVE-2026-53186 and 3 more.