Bug 2311710 (CVE-2024-45013) - CVE-2024-45013 kernel: nvme: move stopping keep-alive into nvme_uninit_ctrl()
Summary: CVE-2024-45013 kernel: nvme: move stopping keep-alive into nvme_uninit_ctrl()
Keywords:
Status: NEW
Alias: CVE-2024-45013
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2311742
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-11 16:20 UTC by OSIDB Bzimport
Modified: 2024-11-06 05:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2024-09-11 16:20:49 UTC
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().


Note You need to log in before you can comment on or make changes to this bug.