CVE-2026-93151

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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

In the Linux kernel, the following vulnerability has been resolved:

nvmet-rdma: fix response resource leak on queue teardown

When an nvme target with rdma transport is removed while I/Os are in flight, a response can be posted but its send completion is never delivered before the connection is torn down. As a result nvmet_rdma_send_done() and nvmet_rdma_release_rsp() are never called for the response, and this leaks the allocated RDMA read/write context and request SGLs.

These leaks are recreated by running blktests nvme/061 with the rdma transport and the siw driver. Kernel kmemleak feature reports them as follows:

unreferenced object 0xffff88812bc490c0 (size 32): comm "kworker/2:1H", pid 409, jiffies 4307744490 backtrace (crc 89afd339): __kmalloc_noprof+0x5f9/0x890 sgl_alloc_order+0x7b/0x380 nvmet_req_alloc_sgls+0x290/0x4f0 [nvmet] nvmet_rdma_map_sgl_keyed+0x241/0x12e0 [nvmet_rdma] nvmet_rdma_handle_command+0x73e/0xb80 [nvmet_rdma] __ib_process_cq+0x149/0x4c0 [ib_core] ib_cq_poll_work+0x49/0x160 [ib_core] process_one_work+0x8b2/0x1640 worker_thread+0x5fd/0xfe0 kthread+0x367/0x460 ret_from_fork+0x655/0x9d0 ret_from_fork_asm+0x1a/0x30

unreferenced object 0xffff88814bd05e80 (size 64): comm "kworker/3:1H", pid 148, jiffies 4295195428 backtrace (crc e35510cb): __kmalloc_noprof+0x5f9/0x890 rdma_rw_ctx_init+0x333/0x1fa0 [ib_core] nvmet_rdma_map_sgl_keyed+0x5c8/0x12e0 [nvmet_rdma] nvmet_rdma_handle_command+0x73e/0xb80 [nvmet_rdma] __ib_process_cq+0x149/0x4c0 [ib_core] ib_cq_poll_work+0x49/0x160 [ib_core] process_one_work+0x8b2/0x1640 worker_thread+0x5fd/0xfe0 kthread+0x367/0x460 ret_from_fork+0x655/0x9d0 ret_from_fork_asm+0x1a/0x30

To avoid the memory leaks, reclaim the memory of the in-flight responses when the queue QP is torn down. Call nvmet_rdma_free_rsp_resources() that frees up the RDMA read/write context and the request SGLs of such responses.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (7)

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

nvmet-rdma: fix response resource leak on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-rdma: fix response resource leak on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvmet-rdma: fix response resource leak on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9584b3c30e4ee8ca315bdc12249cc6c47cf1a482
generic

nvmet-rdma: fix response resource leak on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91cfa74f1f3772e8c3662c064a45d8633e00c78e
generic

nvmet-rdma: fix response resource leak on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5cc3b21729d45b5af8f79891f9dedb7e6b6dbd08
generic

nvmet-rdma: fix response resource leak on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/156ec10a8be2c33b0c279d8b2f4fe8e16fa89ef7
generic

nvmet-rdma: fix response resource leak on queue teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0114dd303b373522dea06053aabae34bdd33a7c4

Vendor Advisories for CVE-2026-93151(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-93151?
CVE-2026-93151 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: nvmet-rdma: fix response resource leak on queue teardown When an nvme target with rdma transport is removed while I/Os are in flight, a response can be posted but its send completion is never delivered before the connection is torn…
When was CVE-2026-93151 disclosed?
CVE-2026-93151 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93151 actively exploited?
CVE-2026-93151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93151?
CVE-2026-93151 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93151?
No fix for CVE-2026-93151 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93151 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-93151?

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

Book a Demo →Browse All CVEs