CVE-2024-56632: nvme-tcp: fix the memleak while create new ctrl failed
In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: fix the memleak while create new ctrl failed
Now while we create new ctrl failed, we have not free the
tagset occupied by admin_q, here try to fix it.
Security readout for executives and security teams
Plain-English summary
A Linux NVMe/TCP error path can leave allocated kernel resources behind when creation of a storage controller fails. Repeated failures could consume resources and reduce system availability. The supplied CVSS score is 7.5, but the sources do not establish data theft, modification, or active exploitation.
Executive priority
Prioritize storage hosts using NVMe/TCP, especially availability-sensitive infrastructure. Patch through supported distribution channels after compatibility testing. Systems not using NVMe/TCP have lower likely exposure. Because exploitation evidence is absent and version boundaries are incomplete, use vendor confirmation to drive emergency-versus-routine scheduling.
Technical view
CVE-2024-56632 is a CWE-401 resource leak in Linux nvme-tcp. When creation of a new controller fails, the admin queue's tagset is not freed. The referenced stable-kernel commits correct that cleanup failure. The CVSS vector rates network reachability, low complexity, no privileges or interaction, and availability-only impact.
Likely exposure
Exposure is limited to Linux systems using NVMe over TCP where controller creation can fail. The bundle identifies Linux 6.7, 6.12.5, and 6.13 as affected, but also contains an ambiguous “0” entry and does not clearly define complete version ranges. Confirm applicability through distribution advisories and kernel changelogs.
Exploitation context
The CVSS vector describes a network-reachable, unauthenticated availability risk. However, the supplied sources provide no evidence of public exploitation or reliable attack conditions, and the CVE is not listed as KEV in the bundle. Treat deliberate remote triggering as unconfirmed.
Researcher notes
The central defect is missing tagset cleanup on the failed new-controller path, not demonstrated memory corruption or confidentiality compromise. Researchers should examine reachability of that failure path, allocation lifetime, and distribution backports without assuming every network-accessible host is exploitable. The provided affected-version data is insufficient for a definitive range statement.
Mitigation direction
Install a vendor-supported kernel containing the referenced nvme-tcp cleanup fix.
Check distribution advisories for the exact fixed package and affected version ranges.
Where operationally feasible, limit NVMe/TCP access to trusted storage networks.
Monitor affected hosts until patched for controller failures and abnormal resource consumption.
Validation and detection
Inventory systems loading or using Linux NVMe/TCP functionality.
Record running kernel and distribution package versions on exposed systems.
Confirm the installed kernel includes either referenced stable fix or a documented backport.
Review logs and monitoring for repeated NVMe/TCP controller creation failures.
Verify resource usage remains stable during legitimate controller failure conditions.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.