CVE-2026-53186

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-25. the CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Sep 7, 2026
No patch confirmed yet.
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13e91fd076306f5d0cdfa14f53d69e37274723c4
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3523e53ff95f1837ec3f57ff7558532bcb2661b7
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f92a285db7ff6e598591ccbfb551be155c5f4d57
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2015038195939eac54a1ee83c9d98ef1a8ccbbce
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d64bc200ebe4f275b27438c6e593903e0b16fe1
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b9ee09d5e849591f17d98c078033dadea967293
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed77cc819ad631264787cade5ae5ec4c535ec6bb
generic

RDMA/srp: bound SRP_RSP sense copy by the received length - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3889517c2ec7f364914aea8209abfff735f7ecde

Vendor Advisories for CVE-2026-53186(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Additional Vendor Advisories

(7)

Data Freshness Timeline

(refreshed 5× in last 7d / 163× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 638 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 23:41 UTCVendor advisory
  11. 2026-08-30 23:41 UTCGHSA enrichment
  12. 2026-08-30 19:40 UTCEG score recompute
  13. 2026-08-30 19:40 UTCVendor advisory
  14. 2026-08-30 19:40 UTCGHSA enrichment
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-28 04:43 UTCVendor advisory
  19. 2026-08-28 04:42 UTCGHSA enrichment
  20. 2026-08-28 00:02 UTCEG score recompute
  21. 2026-08-28 00:02 UTCVendor advisory
  22. 2026-08-28 00:02 UTCGHSA enrichment
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 05:59 UTCVendor advisory
  2. 2026-08-25 05:59 UTCGHSA enrichment
  3. 2026-08-25 01:55 UTCVendor advisory
  4. 2026-08-25 01:55 UTCGHSA enrichment
  5. 2026-08-24 21:52 UTCEG score recompute
  6. 2026-08-24 21:52 UTCVendor advisory
  7. 2026-08-24 21:52 UTCGHSA enrichment
  8. 2026-08-24 13:14 UTCEG score recompute
  9. 2026-08-24 13:14 UTCVendor advisory
  10. 2026-08-24 13:14 UTCGHSA enrichment
  11. 2026-08-24 04:31 UTCVendor advisory
  12. 2026-08-24 04:31 UTCGHSA enrichment
  13. 2026-08-23 23:55 UTCVendor advisory
  14. 2026-08-23 23:54 UTCGHSA enrichment
  15. 2026-08-23 19:52 UTCVendor advisory
  16. 2026-08-23 19:52 UTCGHSA enrichment
  17. 2026-08-23 15:50 UTCVendor advisory
  18. 2026-08-23 15:50 UTCGHSA enrichment
  19. 2026-08-23 11:48 UTCVendor advisory
  20. 2026-08-23 11:48 UTCGHSA enrichment
  21. 2026-08-23 07:46 UTCVendor advisory
  22. 2026-08-23 07:46 UTCGHSA enrichment
  23. 2026-08-23 02:37 UTCEG score recompute
  24. 2026-08-23 02:37 UTCVendor advisory
  25. 2026-08-23 02:36 UTCGHSA enrichment
  26. 2026-08-23 00:19 UTCEPSS rescore
  27. 2026-08-22 22:30 UTCVendor advisory
  28. 2026-08-22 22:30 UTCGHSA enrichment
  29. 2026-08-22 14:51 UTCVendor advisory
  30. 2026-08-22 14:51 UTCGHSA enrichment
  31. 2026-08-22 10:45 UTCVendor advisory
  32. 2026-08-22 10:45 UTCGHSA enrichment
  33. 2026-08-22 01:30 UTCEG score recompute
  34. 2026-08-22 01:30 UTCVendor advisory
  35. 2026-08-22 01:30 UTCGHSA enrichment
  36. 2026-08-21 23:49 UTCEPSS rescore
  37. 2026-08-21 21:28 UTCVendor advisory
  38. 2026-08-21 21:28 UTCGHSA enrichment
  39. 2026-08-21 17:26 UTCVendor advisory
  40. 2026-08-21 17:26 UTCGHSA enrichment
  41. 2026-08-21 13:14 UTCVendor advisory
  42. 2026-08-21 13:14 UTCGHSA enrichment
  43. 2026-08-21 09:12 UTCVendor advisory
  44. 2026-08-21 09:12 UTCGHSA enrichment
  45. 2026-08-21 05:09 UTCVendor advisory
  46. 2026-08-21 05:09 UTCGHSA enrichment
  47. 2026-08-21 00:15 UTCEG score recompute
  48. 2026-08-21 00:15 UTCVendor advisory
  49. 2026-08-21 00:15 UTCGHSA enrichment
  50. 2026-08-20 22:55 UTCEPSS rescore
  51. 2026-08-20 20:08 UTCVendor advisory
  52. 2026-08-20 20:08 UTCGHSA enrichment
  53. 2026-08-20 16:06 UTCVendor advisory
  54. 2026-08-20 16:06 UTCGHSA enrichment
  55. 2026-08-20 11:11 UTCVendor advisory
  56. 2026-08-20 11:11 UTCGHSA enrichment
  57. 2026-08-20 07:09 UTCEG score recompute
  58. 2026-08-20 07:09 UTCVendor advisory
  59. 2026-08-20 07:09 UTCGHSA enrichment
  60. 2026-08-19 17:04 UTCEPSS rescore
  61. 2026-08-19 14:50 UTCVendor advisory
  62. 2026-08-19 14:50 UTCGHSA enrichment
  63. 2026-08-19 10:31 UTCVendor advisory
  64. 2026-08-19 10:30 UTCGHSA enrichment
  65. 2026-08-19 05:42 UTCVendor advisory
  66. 2026-08-19 05:42 UTCGHSA enrichment
  67. 2026-08-19 01:33 UTCEG score recompute
  68. 2026-08-19 01:33 UTCVendor advisory
  69. 2026-08-19 01:33 UTCGHSA enrichment
  70. 2026-08-18 13:48 UTCEPSS rescore
  71. 2026-08-17 17:01 UTCEG score recompute
  72. 2026-08-17 17:01 UTCVendor advisory
  73. 2026-08-17 17:01 UTCGHSA enrichment
  74. 2026-08-17 13:47 UTCEPSS rescore
  75. 2026-08-17 12:59 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-53186?
CVE-2026-53186 is a critical vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/srp: bound SRP_RSP 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…
When was CVE-2026-53186 disclosed?
CVE-2026-53186 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53186 actively exploited?
CVE-2026-53186 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53186?
CVE-2026-53186 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53186?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53186, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53186

Explore →

Is Your Infrastructure Affected by CVE-2026-53186?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.