Security readout for executives and security teams
Plain-English summary
A memory-management flaw in Linux NVMe target authentication can free the same cryptographic key twice after a setup error. This may crash or corrupt an affected kernel and could threaten data confidentiality, integrity, and availability. Risk is concentrated on systems using the nvmet authentication functionality.
Executive priority
Treat as high priority for reachable NVMe target infrastructure using authentication. Patch exposed or business-critical storage systems first. Systems not using nvmet authentication are less likely to encounter this specific path, but version and configuration evidence should support any deferral.
Technical view
An error path in nvmet_setup_dhgroup() frees ctrl->dh_key without setting the pointer to NULL. Reuse of that controller can leave the stale pointer available for a second release in nvmet_destroy_auth(), producing a CWE-415 double free. The cited Linux stable commits nullify the pointer after kfree_sensitive().
Likely exposure
Prioritize Linux systems configured as NVMe targets with authentication enabled, particularly where untrusted clients can reach the service. The bundle identifies affected Linux releases, but its version data is ambiguous; confirm exposure using the running kernel build, distribution advisory, configuration, and cited fixes.
Exploitation context
The supplied CVSS 3.1 score is 8.1 with network reachability, high attack complexity, no required privileges, and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation. Triggering appears dependent on the affected authentication error and controller-lifecycle paths.
Researcher notes
The defect was found by Linux Verification Center using Svace. The essential condition is a stale ctrl->dh_key pointer surviving kfree_sensitive() on an error path and later reaching nvmet_destroy_auth(). The bundle does not establish practical exploitation, reliable impact beyond the CVSS assessment, or exact downstream package boundaries.
Mitigation direction
- Apply a vendor-supported kernel update containing the applicable cited stable fix.
- Review Linux distribution advisories to identify the corrected package for each deployed kernel.
- Restrict NVMe target access to trusted networks and clients while updates are pending.
- Disable unused NVMe target authentication functionality where operationally safe.
Validation and detection
- Inventory systems running Linux NVMe target services and determine whether authentication is configured.
- Record each running kernel version and distribution package release.
- Confirm the installed kernel contains the applicable cited stable commit or vendor backport.
- Verify network controls prevent unauthorized clients from reaching exposed NVMe target services.
- After updating, reboot into the corrected kernel and confirm the active kernel version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-415: 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.
Open ATT&CK lookupCVE-2024-50215 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/c94e965f766321641ec38e4eece9ce8884543244CVE reference, Linux
- https://git.kernel.org/stable/c/c60af16e1d6cc2237d58336546d6adfc067b6b8fCVE reference, Linux
- https://git.kernel.org/stable/c/e61bd51e44409495d75847e9230736593e4c8710CVE reference, Linux
- https://git.kernel.org/stable/c/d2f551b1f72b4c508ab9298419f6feadc3b5d791CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Double Free
Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.