CVE-2021-47074: nvme-loop: fix memory leak in nvme_loop_create_ctrl()
In the Linux kernel, the following vulnerability has been resolved:
nvme-loop: fix memory leak in nvme_loop_create_ctrl()
When creating loop ctrl in nvme_loop_create_ctrl(), if nvme_init_ctrl()
fails, the loop ctrl should be freed before jumping to the "out" label.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47074 is a Linux kernel memory leak in the nvme-loop driver. If controller creation fails during initialization, memory may not be freed. The provided sources do not show active exploitation, a CVSS score, or attacker prerequisites.
Executive priority
Treat this as routine kernel hygiene unless affected storage workflows are important in your environment. There is no source-backed evidence of active exploitation, but unpatched kernel memory leaks can affect reliability on exposed or heavily used systems.
Technical view
The flaw is in nvme_loop_create_ctrl(). When nvme_init_ctrl() fails, the loop controller object should be freed before the function exits through the out label. The Linux kernel references identify stable commits resolving this error-path leak. Impact details beyond memory leakage are not provided.
Likely exposure
Exposure is most relevant to Linux systems with affected kernel versions and nvme-loop functionality present or used. The source bundle lists Linux kernel versions including 4.8 through 5.13-era entries as affected, but distribution-specific status requires vendor confirmation.
Exploitation context
The provided sources do not indicate CISA KEV listing or active exploitation. They also do not define whether exploitation is local, remote, authenticated, or only reachable through specific storage workflows.
Researcher notes
Evidence is limited to the CVE description and Linux stable references. No CVSS, CWE, exploitability prerequisites, or distribution package mapping are included. Avoid assuming remote exploitability or denial-of-service impact beyond the documented memory leak.
Mitigation direction
Apply a Linux kernel update that includes the referenced stable fixes.
Check distribution advisories for the exact fixed package version.
Prioritize systems using NVMe loopback or NVMe over Fabrics testing paths.
If immediate patching is unavailable, review vendor guidance for supported mitigations.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and storage nodes.
Identify systems where nvme-loop is enabled, loaded, or operationally required.
Confirm the vendor kernel includes one of the referenced stable fixes.
Review reliability telemetry for repeated nvme-loop controller initialization failures.
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-2021-47074 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.