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

> A use-after-free in the Linux kernel NVMe driver can cause a kernel panic when the driver is unloaded after a connection failure.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-45013, DEBIAN-CVE-2024-45013, GHSA-4j5q-jrmv-h6pp, UBUNTU-CVE-2024-45013

## What is CVE-2024-45013?

CVE-2024-45013 is a critical use after free vulnerability in Linux kernel, published on 11 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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().

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-45013?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-45013?

Apply the vendor's patch.

## Is CVE-2024-45013 being exploited?

There is no known exploitation of CVE-2024-45013 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45013 and fix it if it is affected.

What it is: CVE-2024-45013 is a critical use after free vulnerability in Linux kernel, published on 11 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45013 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45013/ (Markdown: https://insights.sbomify.com/CVE-2024-45013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45013
- OSV: https://osv.dev/vulnerability/CVE-2024-45013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45013/
Summaries are generated and may contain mistakes; the official description above is the record.