CVE-2026-23261

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

nvme-fc: release admin tagset if init fails

nvme_fabrics creates an NVMe/FC controller in following path:

nvmf_dev_write() -> nvmf_create_ctrl() -> nvme_fc_create_ctrl() -> nvme_fc_init_ctrl()

nvme_fc_init_ctrl() allocates the admin blk-mq resources right after nvme_add_ctrl() succeeds. If any of the subsequent steps fail (changing the controller state, scheduling connect work, etc.), we jump to the fail_ctrl path, which tears down the controller references but never frees the admin queue/tag set. The leaked blk-mq allocations match the kmemleak report seen during blktests nvme/fc.

Check ctrl->ctrl.admin_tagset in the fail_ctrl path and call nvme_remove_admin_tag_set() when it is set so that all admin queue allocations are reclaimed whenever controller setup aborts.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

March 18, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 6, 2026
No patch confirmed yet.
generic

nvme-fc: release admin tagset if init fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-fc: release admin tagset if init fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-fc: release admin tagset if init fails - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-fc: release admin tagset if init fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c54d3f5ebbc5982daaa004260242dc07ac943ea

Patch Availability(8)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.73-1~bpo12+1 (12 versions)6.12.73-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)6.18.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(9)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-23261?
CVE-2026-23261 is a medium vulnerability published on March 18, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-fc: release admin tagset if init fails nvme_fabrics creates an NVMe/FC controller in following path: nvmfdevwrite() -> nvmfcreatectrl() -> nvmefccreate_ctrl() -> nvmefcinit_ctrl() nvmefcinit_ctrl() allocates the admin blk-mq…
When was CVE-2026-23261 disclosed?
CVE-2026-23261 was first published in the National Vulnerability Database on March 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23261 actively exploited?
CVE-2026-23261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-23261?
CVE-2026-23261 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23261?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23261, 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-23261

Explore →

Is Your Infrastructure Affected by CVE-2026-23261?

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