| 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-50081: blk-mq: setup queue ->tag_set before initializing hctx |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| blk-mq: setup queue ->tag_set before initializing hctx |
| |
| Commit 7b815817aa58 ("blk-mq: add helper for checking if one CPU is mapped to specified hctx") |
| needs to check queue mapping via tag set in hctx's cpuhp handler. |
| |
| However, q->tag_set may not be setup yet when the cpuhp handler is |
| enabled, then kernel oops is triggered. |
| |
| Fix the issue by setup queue tag_set before initializing hctx. |
| |
| The Linux kernel CVE team has assigned CVE-2024-50081 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.10 with commit 7b815817aa58d2e2101feb2fcf64c60cae0b2695 and fixed in 6.11.5 with commit d28b256db525d9432bc3eb2c8d83f7d3f5e1cc87 |
| Issue introduced in 6.10 with commit 7b815817aa58d2e2101feb2fcf64c60cae0b2695 and fixed in 6.12 with commit c25c0c9035bb8b28c844dfddeda7b8bdbcfcae95 |
| |
| 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-50081 |
| 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: |
| block/blk-mq.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/d28b256db525d9432bc3eb2c8d83f7d3f5e1cc87 |
| https://git.kernel.org/stable/c/c25c0c9035bb8b28c844dfddeda7b8bdbcfcae95 |
