LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23360: nvme: fix admin queue leak on controller reset

In the Linux kernel, the following vulnerability has been resolved: nvme: fix admin queue leak on controller reset When nvme_alloc_admin_tag_set() is called during a controller reset, a previous admin queue may still exist. Release it properly before allocating a new one to avoid orphaning the old queue. This fixes a regression introduced by commit 03b3bcd319b3 ("nvme: fix admin request_queue lifetime").

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a resource leak in NVMe controller reset handling. During reset, an old admin queue could be left orphaned before a new one is allocated. The public sources do not provide CVSS, CWE, exploitability, or business-impact detail, so urgency should be based on NVMe usage and vendor kernel status.

Executive priority

Treat as a targeted Linux infrastructure maintenance item until more risk data exists. Prioritize storage-heavy servers and cloud images using NVMe, but do not escalate as an active-exploitation emergency based on the provided evidence.

Technical view

The NVMe driver path nvme_alloc_admin_tag_set() may allocate a new admin tag set during controller reset while a previous admin queue still exists. The fix releases the existing queue first. The CVE states this regression was introduced by commit 03b3bcd319b3, with multiple stable-kernel fix commits referenced.

Likely exposure

Exposure is most relevant to Linux systems using NVMe storage and kernel versions or downstream builds containing the regression. The bundle lists Linux kernel version and commit identifiers, but distro-specific package status is not provided.

Exploitation context

No source in the bundle states active exploitation, public exploit availability, remote attackability, or privilege requirements. The described failure mode is an orphaned kernel queue during reset, suggesting operational stability risk rather than confirmed code execution.

Researcher notes

The key research gap is exploitability. Sources identify a regression and fix, but not trigger conditions beyond controller reset, required privileges, impact severity, or whether the leak is reliably reachable from unprivileged contexts.

Mitigation direction

  • Check the running kernel against vendor advisories for CVE-2026-23360.
  • Prioritize Linux hosts using NVMe storage or frequent controller reset paths.
  • Apply vendor-supported kernel updates containing the referenced stable fixes.
  • Use normal maintenance windows if storage availability risk is operationally sensitive.

Validation and detection

  • Inventory Linux kernel versions across NVMe-backed systems.
  • Map distro kernel packages to the referenced upstream stable commits.
  • Review kernel logs for NVMe controller reset or queue-related anomalies.
  • Confirm patched systems run a vendor kernel that includes the fix.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23360 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxff037b5f47eeccc1636c03f84cd47db094eb73c9, 4896491c497226022626c3acc46044fd182f943c, a505f0ba36ab24176c300d7ff56aff85c2977e6c, e8061d02b49c5c901980f58d91e96580e9a14acf, 03b3bcd319b3ab5182bc9aaa0421351572c78ac0, 03b3bcd319b3ab5182bc9aaa0421351572c78ac0, 03b3bcd319b3ab5182bc9aaa0421351572c78ac0, e7dac681790556c131854b97551337aa8042215b, 6.1.167, 6.6.120, 6.12.62, 6.17.12unaffected
LinuxLinux6.18, 0, 6.1.168, 6.6.131, 6.12.77, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.