| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-45013: nvme: move stopping keep-alive into nvme_uninit_ctrl() |
| |
| 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(). |
| |
| The Linux kernel CVE team has assigned CVE-2024-45013 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.7 with commit 3af755a46881c32fecaecfdeaf3a8f0a869deca5 and fixed in 6.10.7 with commit 4101af98ab573554c4225e328d506fec2a74bc54 |
| Issue introduced in 6.7 with commit 3af755a46881c32fecaecfdeaf3a8f0a869deca5 and fixed in 6.11 with commit a54a93d0e3599b05856971734e15418ac551a14c |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2024-45013 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/nvme/host/core.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/4101af98ab573554c4225e328d506fec2a74bc54 |
| https://git.kernel.org/stable/c/a54a93d0e3599b05856971734e15418ac551a14c |
