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

Published Sep 11, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

nvme: move stopping keep-alive into nvmeuninitctrl()

Commit 4733b65d82bd ("nvme: start keep-alive after admin queue setup") moves starting keep-alive from nvmestartctrl() into nvmeinitctrlfinish(), but don't move stopping keep-alive into nvmeuninitctrl(), 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 nvmeuninitctrl().

This way is reasonable because keep-alive is now started in nvmeinitctrlfinish().

Affected Software

6 affected componentsFixes available
Linux Linux kernel>=6.7<6.10.7
Linux Linux kernel=6.11-rc1
Linux Linux kernel=6.11-rc2
Linux Linux kernel=6.11-rc3
Linux Linux kernel=6.11-rc4
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.22-1Fixed in 6.12.25-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch 4733b65d82bd
  3. Compensating control

    Apply the kernel patch that moves NVMe keep-alive shutdown into nvme_uninit_ctrl() to prevent a use-after-free/kernel panic when the NVMe controller fails to start (e.g., during the scenario referenced as nvme/004 and connection failure).

Event History

Sep 11, 2024
CVE Published
via MITRE·03:13 PM
Data Sourced
via MITRE·03:13 PM
DescriptionSeverity
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 13, 2025
Data Sourced
via Ubuntu·06:30 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-45013?

CVE-2024-45013 has a medium severity rating due to the impact on system stability during NVMe controller management.

2

How do I fix CVE-2024-45013?

To mitigate CVE-2024-45013, upgrade to a patched version of the Linux Kernel, such as 5.10.223-1, 6.1.123-1, or later.

3

Which versions of the Linux Kernel are affected by CVE-2024-45013?

CVE-2024-45013 affects Linux Kernel versions from 6.7 up to and including 6.10.7, and several 6.11 release candidates.

4

What was the cause of CVE-2024-45013?

CVE-2024-45013 was caused by the incorrect handling of the NVMe controller's keep-alive operation during initialization.

5

Is CVE-2024-45013 present in Debian Linux distributions?

Yes, CVE-2024-45013 can affect Debian Linux distributions running on the vulnerable versions of the Linux Kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203