CVE-2024-42276: nvme-pci: add missing condition check for existence of mapped data
In the Linux kernel, the following vulnerability has been resolved:
nvme-pci: add missing condition check for existence of mapped data
nvme_map_data() is called when request has physical segments, hence
the nvme_unmap_data() should have same condition to avoid dereference.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel NVMe PCI storage driver flaw. The kernel fix adds a missing check before unmapping request data, preventing an invalid dereference when mapped data does not exist. The sources do not provide CVSS, confirmed impact, or active exploitation evidence.
Executive priority
Track and remediate through normal kernel patch management unless local vendor guidance raises severity. Give higher priority to production systems dependent on NVMe storage and vendor appliances where kernel faults could disrupt service.
Technical view
CVE-2024-42276 affects Linux nvme-pci logic where nvme_unmap_data() lacked the same physical-segment condition used by nvme_map_data(). The fix adds the missing existence check. Public records list Linux kernel versions as affected and cite stable kernel commits plus Debian and Siemens advisories.
Likely exposure
Exposure is most relevant to Linux systems using the nvme-pci driver for PCIe NVMe storage, including servers, workstations, appliances, and embedded products that ship affected kernels. Confirm exposure through kernel version, distribution advisories, and hardware or module inventory.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The cited sources do not claim active exploitation, public exploit availability, remote reachability, required privileges, or a complete impact rating.
Researcher notes
Evidence is limited to a kernel fix description and downstream advisories. Treat impact details beyond invalid dereference prevention as unconfirmed. Do not assume exploitability, privilege requirements, or attack vector without vendor or maintainer clarification.
Mitigation direction
Update Linux kernels using vendor-supported packages containing the stable fix.
Review Debian LTS and product vendor advisories for backported fixed packages.
Prioritize systems using PCIe NVMe storage or affected embedded Linux images.
For appliances, obtain fixed firmware or kernel updates from the vendor.
Validation and detection
Inventory running kernel versions across Linux hosts and appliances.
Check whether nvme-pci is loaded or PCIe NVMe storage is present.
Map kernel builds to vendor advisories or upstream stable fix commits.
Confirm patched hosts boot the intended fixed kernel after update.
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-2024-42276 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.