CVE-2026-53186: Linux kernel · Out-of-bounds Read
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical · fixed in f92a285db7ff6e598591ccbfb551be155c5f4d57 : patch Linux kernel as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in f92a285db7ff6e598591ccbfb551be155c5f4d57, ed77cc819ad631264787cade5ae5ec4c535ec6bb, 2015038195939eac54a1ee83c9d98ef1a8ccbbce +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/3889517c2ec7f364914aea8209abfff735f7ecde (opens in a new tab)
- git.kernel.org/stable/c/ed77cc819ad631264787cade5ae5ec4c535ec6bb (opens in a new tab)
- git.kernel.org/stable/c/0b9ee09d5e849591f17d98c078033dadea967293 (opens in a new tab)
- git.kernel.org/stable/c/0d64bc200ebe4f275b27438c6e593903e0b16fe1 (opens in a new tab)
- git.kernel.org/stable/c/2015038195939eac54a1ee83c9d98ef1a8ccbbce (opens in a new tab)
- git.kernel.org/stable/c/f92a285db7ff6e598591ccbfb551be155c5f4d57 (opens in a new tab)
- git.kernel.org/stable/c/3523e53ff95f1837ec3f57ff7558532bcb2661b7 (opens in a new tab)
- git.kernel.org/stable/c/13e91fd076306f5d0cdfa14f53d69e37274723c4 (opens in a new tab)