Security readout for executives and security teams
Plain-English summary
A Linux NVMe driver error can free the same memory twice when namespace identification fails. This may corrupt kernel memory or crash a system. The supplied evidence documents detection during kernel testing, not a real-world attack or proven code execution.
Executive priority
Treat as a high-priority kernel maintenance issue for affected NVMe systems, especially availability-sensitive servers. Accelerate normal patching, but the evidence does not justify an emergency response based on active exploitation.
Technical view
In ns_update_nuse(), failure of nvme_identify_ns() caused a second kfree() after that function had already freed struct nvme_id_ns. KASAN observed the double-free during blktests nvme/045 on Linux 6.8-rc7. The referenced kernel changes prevent the second free on failure.
Likely exposure
Exposure is most likely on affected Linux 6.8-series kernels using NVMe where namespace identification can fail. The bundle identifies versions 6.8 through the listed correction boundaries, but does not establish individual distribution package status. Systems without NVMe use are less likely to reach this path.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. However, the supplied sources provide no evidence of active exploitation, and the CVE is not listed as KEV. The documented observation occurred under KASAN during testing.
Researcher notes
The root cause and correction are well documented, but practical attacker control over the failure condition is not established in the bundle. CVSS indicates potentially severe confidentiality, integrity, and availability impact; the cited observation only proves a KASAN-detected double-free in testing.
Mitigation direction
- Install a vendor-supported kernel containing one of the referenced corrective commits.
- Check distribution security guidance for the precise fixed package version.
- Prioritize NVMe hosts running affected 6.8-series kernels.
- Reboot systems after updating so the corrected kernel is active.
Validation and detection
- Inventory running kernel versions and identify hosts using NVMe storage.
- Verify the active kernel includes the applicable referenced correction.
- Review kernel logs for KASAN double-free reports or NVMe identification failures.
- After remediation, confirm hosts rebooted into the vendor-fixed kernel.
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.
CVE-2024-27392 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
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
1 official scoreWe 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
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/534f9dc7fe495b3f9cc84363898ac50c5a25fccbCVE reference, Linux
- https://git.kernel.org/stable/c/8d0d2447394b13fb22a069f0330f9c49b7fff9d3CVE reference, Linux
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.