CVE-2026-53186 — Linux kernel RDMA/SRP out-of-bounds read via SRP_RSP sense data
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+6
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 2.6.15≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < 13e91fd076306f5d0cdfa14f53d69e37274723c4≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < 3523e53ff95f1837ec3f57ff7558532bcb2661b7≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < f92a285db7ff6e598591ccbfb551be155c5f4d57≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < 2015038195939eac54a1ee83c9d98ef1a8ccbbce≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < 0d64bc200ebe4f275b27438c6e593903e0b16fe1≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < 0b9ee09d5e849591f17d98c078033dadea967293≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < ed77cc819ad631264787cade5ae5ec4c535ec6bb and 1 more≥ aef9ec39c47f0cece886ddd6b53c440321e0b2a6 and < 3889517c2ec7f364914aea8209abfff735f7ecde |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 7.1-rc5version 7.1-rc7version 7.1-rc6≥ 2.6.15 and < 5.10.259version 7.1-rc4version 7.1-rc3version 7.1-rc2version 7.1-rc1 and 6 more≥ 6.19 and < 7.0.13≥ 6.13 and < 6.18.36≥ 6.7 and < 6.12.94≥ 6.2 and < 6.6.143≥ 5.16 and < 6.1.176≥ 5.11 and < 5.15.210 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.1 | CVSS 3.1 | Critical | 3.9 | 5.2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 9.1 | CVSS 3.1 | Critical | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.51%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Analysis and videos
CVE-2026-53186: Linux kernel RDMA/SRP out-of-bounds read via SRP_RSP sense data
A flaw in the Linux kernel ib_srp initiator lets a malicious or compromised SRP target trigger a read past the receive buffer when processing SRP_RSP sense data. The record gives a CNA CVSS 3.1 base score of 9.1 and lists affected kernel ranges with upstream stable fixes. No confirmed exploitation appears in the sources consulted.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- Fix documented
- CVSS changed · 9.1
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/3889517c2ec7f364914aea8209abfff735f7ecde
- git.kernel.org/stable/c/2015038195939eac54a1ee83c9d98ef1a8ccbbce
- git.kernel.org/stable/c/13e91fd076306f5d0cdfa14f53d69e37274723c4
- git.kernel.org/stable/c/0b9ee09d5e849591f17d98c078033dadea967293
- git.kernel.org/stable/c/ed77cc819ad631264787cade5ae5ec4c535ec6bb
- git.kernel.org/stable/c/0d64bc200ebe4f275b27438c6e593903e0b16fe1
- git.kernel.org/stable/c/3523e53ff95f1837ec3f57ff7558532bcb2661b7
- git.kernel.org/stable/c/f92a285db7ff6e598591ccbfb551be155c5f4d57
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-53186 is "Linux kernel RDMA/SRP out-of-bounds read via SRP_RSP sense data", rated Critical. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.1 describes technical severity. EPSS 0.51% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.