| 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-50184: virtio_pmem: Check device status before requesting flush |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| virtio_pmem: Check device status before requesting flush |
| |
| If a pmem device is in a bad status, the driver side could wait for |
| host ack forever in virtio_pmem_flush(), causing the system to hang. |
| |
| So add a status check in the beginning of virtio_pmem_flush() to return |
| early if the device is not activated. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50184 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.3 with commit 6e84200c0a2994b991259d19450eee561029bf70 and fixed in 5.4.285 with commit 59ac565c6277d4be6661e81ea6a7f3ca2c5e4e36 |
| Issue introduced in 5.3 with commit 6e84200c0a2994b991259d19450eee561029bf70 and fixed in 5.10.227 with commit 4ce662fe4be6fbc2595d9ef4888b2b6e778c99ed |
| Issue introduced in 5.3 with commit 6e84200c0a2994b991259d19450eee561029bf70 and fixed in 5.15.168 with commit 9a2bc9b6f929a2ce1ebe4d1a796ddab37568c5b4 |
| Issue introduced in 5.3 with commit 6e84200c0a2994b991259d19450eee561029bf70 and fixed in 6.1.113 with commit 6a5ca0ab94e13a1474bf7ad8437a975c2193618f |
| Issue introduced in 5.3 with commit 6e84200c0a2994b991259d19450eee561029bf70 and fixed in 6.6.57 with commit b01793cc63dd39c8f12b9a3d8dc115fbebb19e2a |
| Issue introduced in 5.3 with commit 6e84200c0a2994b991259d19450eee561029bf70 and fixed in 6.11.4 with commit ce7a3a62cc533c922072f328fd2ea2fd7cb893d4 |
| Issue introduced in 5.3 with commit 6e84200c0a2994b991259d19450eee561029bf70 and fixed in 6.12 with commit e25fbcd97cf52c3c9824d44b5c56c19673c3dd50 |
| |
| 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-50184 |
| 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/nvdimm/nd_virtio.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/59ac565c6277d4be6661e81ea6a7f3ca2c5e4e36 |
| https://git.kernel.org/stable/c/4ce662fe4be6fbc2595d9ef4888b2b6e778c99ed |
| https://git.kernel.org/stable/c/9a2bc9b6f929a2ce1ebe4d1a796ddab37568c5b4 |
| https://git.kernel.org/stable/c/6a5ca0ab94e13a1474bf7ad8437a975c2193618f |
| https://git.kernel.org/stable/c/b01793cc63dd39c8f12b9a3d8dc115fbebb19e2a |
| https://git.kernel.org/stable/c/ce7a3a62cc533c922072f328fd2ea2fd7cb893d4 |
| https://git.kernel.org/stable/c/e25fbcd97cf52c3c9824d44b5c56c19673c3dd50 |
