LiveActive security incident?Get immediate response
CVE Record

CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl()

In the Linux kernel, the following vulnerability has been resolved: nvme: move stopping keep-alive into nvme_uninit_ctrl() Commit 4733b65d82bd ("nvme: start keep-alive after admin queue setup") moves starting keep-alive from nvme_start_ctrl() into nvme_init_ctrl_finish(), but don't move stopping keep-alive into nvme_uninit_ctrl(), so keep-alive work can be started and keep pending after failing to start controller, finally use-after-free is triggered if nvme host driver is unloaded. This patch fixes kernel panic when running nvme/004 in case that connection failure is triggered, by moving stopping keep-alive into nvme_uninit_ctrl(). This way is reasonable because keep-alive is now started in nvme_init_ctrl_finish().

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux NVMe controller cleanup flaw can leave keep-alive work running after controller startup fails. Unloading the NVMe host driver can then access freed memory and panic the kernel. This creates serious availability risk; the supplied CVSS also indicates possible confidentiality and integrity impact, although the source description only demonstrates a use-after-free and kernel panic.

Executive priority

Treat as urgent on affected NVMe-enabled infrastructure, especially systems using remote or failure-prone controller connections. Schedule vendor-approved kernel updates promptly. Broader emergency action should depend on confirmed affected versions and reachable NVMe configurations because active exploitation is not established.

Technical view

Keep-alive work starts during nvme_init_ctrl_finish(), but previously was not stopped in nvme_uninit_ctrl() when controller startup failed. Pending work could survive controller cleanup and cause a use-after-free when the NVMe host driver unloaded. The referenced kernel patches move keep-alive shutdown into nvme_uninit_ctrl().

Likely exposure

Exposure requires an affected Linux kernel, NVMe host functionality, a controller connection failure, and subsequent host-driver unloading. The supplied affected-version data lists 6.7, 6.10.7, and 6.11, but also contains an ambiguous "0" entry. Confirm exact distribution package exposure with the vendor.

Exploitation context

The bundle reports CVSS 3.1 score 9.8 and a network attack vector, but provides no exploit narrative beyond the failure-and-unload sequence. KEV is false, and no supplied source establishes active exploitation or a public weaponized exploit. Practical remote exploitability therefore remains unclear from the available evidence.

Researcher notes

The demonstrated condition is a lifecycle race: keep-alive work remains pending after failed controller initialization, then references freed state during driver unload. The fix aligns keep-alive shutdown with controller uninitialization. The supplied CVSS impact claims are broader than the described kernel-panic outcome, so confidentiality and integrity consequences need further validation.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced NVMe keep-alive cleanup fix.
  • Confirm fixed package versions through the Linux distribution or appliance vendor's security guidance.
  • Prioritize systems using NVMe host drivers or connecting to remote NVMe controllers.
  • If updates are unavailable, request vendor-approved mitigations; none are specified in the supplied sources.

Validation and detection

  • Inventory Linux kernel versions and systems using NVMe host functionality.
  • Check vendor changelogs or kernel source history for either referenced stable fix.
  • Confirm the running kernel matches the updated package after remediation.
  • Regression-test controller connection failure and driver cleanup safely in staging.
  • Review kernel logs for NVMe-related panics following connection failures or driver unloading.
Prepared
Confidence
high
Sources
4

Public sources used

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-45013 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-45013Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3af755a46881c32fecaecfdeaf3a8f0a869deca5, 3af755a46881c32fecaecfdeaf3a8f0a869deca5unaffected
LinuxLinux6.7, 0, 6.10.7, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.