# 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.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 19 Oct 2026
- **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, ROOT-OS-UBUNTU-2204-CVE-2026-53186, ROOT-OS-UBUNTU-2404-CVE-2026-53186, UBUNTU-CVE-2026-53186

## 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 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-53186?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-53186?

Apply the vendor's patch.

## 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

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53186 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-53186 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53186/ (Markdown: https://insights.sbomify.com/CVE-2026-53186/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53186
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53186
- OSV: https://osv.dev/vulnerability/CVE-2026-53186

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53186/
Summaries are generated and may contain mistakes; the official description above is the record.