CVE-2026-53186

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-25. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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(high)
EPSS
41.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (8)

Auto-updated Jun 28, 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/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/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
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/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/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/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

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.

Data Freshness Timeline

(refreshed 133× in last 7d / 173× 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 173 total refreshes for this CVE.

  1. 2026-07-07 01:47 UTCEG score recompute
  2. 2026-07-07 01:47 UTCVendor advisory
  3. 2026-07-07 01:47 UTCGHSA enrichment
  4. 2026-07-06 21:44 UTCEG score recompute
  5. 2026-07-06 21:44 UTCVendor advisory
  6. 2026-07-06 21:44 UTCGHSA enrichment
  7. 2026-07-06 17:42 UTCEG score recompute
  8. 2026-07-06 17:42 UTCVendor advisory
  9. 2026-07-06 17:41 UTCGHSA enrichment
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 13:37 UTCEG score recompute
  13. 2026-07-06 13:37 UTCVendor advisory
  14. 2026-07-06 13:37 UTCGHSA enrichment
  15. 2026-07-06 09:35 UTCEG score recompute
  16. 2026-07-06 09:35 UTCVendor advisory
  17. 2026-07-06 09:35 UTCGHSA enrichment
  18. 2026-07-06 05:30 UTCEG score recompute
  19. 2026-07-06 05:30 UTCVendor advisory
  20. 2026-07-06 05:30 UTCGHSA enrichment
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 01:28 UTCEG score recompute
  24. 2026-07-06 01:28 UTCVendor advisory
  25. 2026-07-06 01:28 UTCGHSA enrichment
Show 75 more
  1. 2026-07-05 21:27 UTCEG score recompute
  2. 2026-07-05 21:27 UTCVendor advisory
  3. 2026-07-05 21:27 UTCGHSA enrichment
  4. 2026-07-05 17:25 UTCEG score recompute
  5. 2026-07-05 17:25 UTCVendor advisory
  6. 2026-07-05 17:25 UTCGHSA enrichment
  7. 2026-07-05 13:22 UTCEG score recompute
  8. 2026-07-05 13:22 UTCVendor advisory
  9. 2026-07-05 13:22 UTCGHSA enrichment
  10. 2026-07-05 09:20 UTCEG score recompute
  11. 2026-07-05 09:20 UTCVendor advisory
  12. 2026-07-05 09:19 UTCGHSA enrichment
  13. 2026-07-05 05:17 UTCEG score recompute
  14. 2026-07-05 05:17 UTCVendor advisory
  15. 2026-07-05 05:17 UTCGHSA enrichment
  16. 2026-07-05 02:31 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-05 01:16 UTCEG score recompute
  19. 2026-07-05 01:16 UTCVendor advisory
  20. 2026-07-05 01:15 UTCGHSA enrichment
  21. 2026-07-04 20:59 UTCEG score recompute
  22. 2026-07-04 20:59 UTCVendor advisory
  23. 2026-07-04 20:59 UTCGHSA enrichment
  24. 2026-07-04 16:56 UTCEG score recompute
  25. 2026-07-04 16:56 UTCVendor advisory
  26. 2026-07-04 16:56 UTCGHSA enrichment
  27. 2026-07-04 12:54 UTCEG score recompute
  28. 2026-07-04 12:54 UTCVendor advisory
  29. 2026-07-04 12:54 UTCGHSA enrichment
  30. 2026-07-04 08:53 UTCEG score recompute
  31. 2026-07-04 08:53 UTCVendor advisory
  32. 2026-07-04 08:53 UTCGHSA enrichment
  33. 2026-07-04 06:31 UTCEPSS rescore
  34. 2026-07-04 06:31 UTCEPSS rescore
  35. 2026-07-04 04:49 UTCEG score recompute
  36. 2026-07-04 04:49 UTCVendor advisory
  37. 2026-07-04 04:49 UTCGHSA enrichment
  38. 2026-07-04 00:45 UTCEG score recompute
  39. 2026-07-04 00:45 UTCVendor advisory
  40. 2026-07-04 00:45 UTCGHSA enrichment
  41. 2026-07-03 20:42 UTCEG score recompute
  42. 2026-07-03 20:42 UTCVendor advisory
  43. 2026-07-03 20:42 UTCGHSA enrichment
  44. 2026-07-03 16:39 UTCEG score recompute
  45. 2026-07-03 16:39 UTCVendor advisory
  46. 2026-07-03 16:39 UTCGHSA enrichment
  47. 2026-07-03 12:37 UTCEG score recompute
  48. 2026-07-03 12:37 UTCVendor advisory
  49. 2026-07-03 12:37 UTCGHSA enrichment
  50. 2026-07-03 07:35 UTCEG score recompute
  51. 2026-07-03 07:35 UTCVendor advisory
  52. 2026-07-03 07:35 UTCGHSA enrichment
  53. 2026-07-03 03:32 UTCEG score recompute
  54. 2026-07-03 03:32 UTCVendor advisory
  55. 2026-07-03 03:32 UTCGHSA enrichment
  56. 2026-07-02 23:29 UTCEG score recompute
  57. 2026-07-02 23:29 UTCVendor advisory
  58. 2026-07-02 23:29 UTCGHSA enrichment
  59. 2026-07-02 19:27 UTCEG score recompute
  60. 2026-07-02 19:27 UTCVendor advisory
  61. 2026-07-02 19:27 UTCGHSA enrichment
  62. 2026-07-02 15:26 UTCEG score recompute
  63. 2026-07-02 15:26 UTCVendor advisory
  64. 2026-07-02 15:26 UTCGHSA enrichment
  65. 2026-07-02 11:24 UTCEG score recompute
  66. 2026-07-02 11:24 UTCVendor advisory
  67. 2026-07-02 11:24 UTCGHSA enrichment
  68. 2026-07-02 07:22 UTCEG score recompute
  69. 2026-07-02 07:22 UTCVendor advisory
  70. 2026-07-02 07:22 UTCGHSA enrichment
  71. 2026-07-02 03:20 UTCEG score recompute
  72. 2026-07-02 03:20 UTCVendor advisory
  73. 2026-07-02 03:20 UTCGHSA enrichment
  74. 2026-07-01 23:18 UTCEG score recompute
  75. 2026-07-01 23:18 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 July 6, 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 41.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53186?
CVE-2026-53186 has a CVSS v3 base score of 9.1 (NVD).
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

Explore the affected products and dependency analysis for 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.