| 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-26742: scsi: smartpqi: Fix disable_managed_interrupts |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: smartpqi: Fix disable_managed_interrupts |
| |
| Correct blk-mq registration issue with module parameter |
| disable_managed_interrupts enabled. |
| |
| When we turn off the default PCI_IRQ_AFFINITY flag, the driver needs to |
| register with blk-mq using blk_mq_map_queues(). The driver is currently |
| calling blk_mq_pci_map_queues() which results in a stack trace and possibly |
| undefined behavior. |
| |
| Stack Trace: |
| [ 7.860089] scsi host2: smartpqi |
| [ 7.871934] WARNING: CPU: 0 PID: 238 at block/blk-mq-pci.c:52 blk_mq_pci_map_queues+0xca/0xd0 |
| [ 7.889231] Modules linked in: sd_mod t10_pi sg uas smartpqi(+) crc32c_intel scsi_transport_sas usb_storage dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse |
| [ 7.924755] CPU: 0 PID: 238 Comm: kworker/0:3 Not tainted 4.18.0-372.88.1.el8_6_smartpqi_test.x86_64 #1 |
| [ 7.944336] Hardware name: HPE ProLiant DL380 Gen10/ProLiant DL380 Gen10, BIOS U30 03/08/2022 |
| [ 7.963026] Workqueue: events work_for_cpu_fn |
| [ 7.978275] RIP: 0010:blk_mq_pci_map_queues+0xca/0xd0 |
| [ 7.978278] Code: 48 89 de 89 c7 e8 f6 0f 4f 00 3b 05 c4 b7 8e 01 72 e1 5b 31 c0 5d 41 5c 41 5d 41 5e 41 5f e9 7d df 73 00 31 c0 e9 76 df 73 00 <0f> 0b eb bc 90 90 0f 1f 44 00 00 41 57 49 89 ff 41 56 41 55 41 54 |
| [ 7.978280] RSP: 0018:ffffa95fc3707d50 EFLAGS: 00010216 |
| [ 7.978283] RAX: 00000000ffffffff RBX: 0000000000000000 RCX: 0000000000000010 |
| [ 7.978284] RDX: 0000000000000004 RSI: 0000000000000000 RDI: ffff9190c32d4310 |
| [ 7.978286] RBP: 0000000000000000 R08: ffffa95fc3707d38 R09: ffff91929b81ac00 |
| [ 7.978287] R10: 0000000000000001 R11: ffffa95fc3707ac0 R12: 0000000000000000 |
| [ 7.978288] R13: ffff9190c32d4000 R14: 00000000ffffffff R15: ffff9190c4c950a8 |
| [ 7.978290] FS: 0000000000000000(0000) GS:ffff9193efc00000(0000) knlGS:0000000000000000 |
| [ 7.978292] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 |
| [ 8.172814] CR2: 000055d11166c000 CR3: 00000002dae10002 CR4: 00000000007706f0 |
| [ 8.172816] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 |
| [ 8.172817] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 |
| [ 8.172818] PKRU: 55555554 |
| [ 8.172819] Call Trace: |
| [ 8.172823] blk_mq_alloc_tag_set+0x12e/0x310 |
| [ 8.264339] scsi_add_host_with_dma.cold.9+0x30/0x245 |
| [ 8.279302] pqi_ctrl_init+0xacf/0xc8e [smartpqi] |
| [ 8.294085] ? pqi_pci_probe+0x480/0x4c8 [smartpqi] |
| [ 8.309015] pqi_pci_probe+0x480/0x4c8 [smartpqi] |
| [ 8.323286] local_pci_probe+0x42/0x80 |
| [ 8.337855] work_for_cpu_fn+0x16/0x20 |
| [ 8.351193] process_one_work+0x1a7/0x360 |
| [ 8.364462] ? create_worker+0x1a0/0x1a0 |
| [ 8.379252] worker_thread+0x1ce/0x390 |
| [ 8.392623] ? create_worker+0x1a0/0x1a0 |
| [ 8.406295] kthread+0x10a/0x120 |
| [ 8.418428] ? set_kthread_struct+0x50/0x50 |
| [ 8.431532] ret_from_fork+0x1f/0x40 |
| [ 8.444137] ---[ end trace 1bf0173d39354506 ]--- |
| |
| The Linux kernel CVE team has assigned CVE-2024-26742 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.0 with commit cf15c3e734e8d25de7b4d9170f5a69ace633a583 and fixed in 6.1.80 with commit 3c31b18a8dd8b7bf36af1cd723d455853b8f94fe |
| Issue introduced in 6.0 with commit cf15c3e734e8d25de7b4d9170f5a69ace633a583 and fixed in 6.6.19 with commit 4f5b15c15e6016efb3e14582d02cc4ddf57227df |
| Issue introduced in 6.0 with commit cf15c3e734e8d25de7b4d9170f5a69ace633a583 and fixed in 6.7.7 with commit b9433b25cb06c415c9cb24782599649a406c8d6d |
| Issue introduced in 6.0 with commit cf15c3e734e8d25de7b4d9170f5a69ace633a583 and fixed in 6.8 with commit 5761eb9761d2d5fe8248a9b719efc4d8baf1f24a |
| |
| 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-26742 |
| 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/scsi/smartpqi/smartpqi_init.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/3c31b18a8dd8b7bf36af1cd723d455853b8f94fe |
| https://git.kernel.org/stable/c/4f5b15c15e6016efb3e14582d02cc4ddf57227df |
| https://git.kernel.org/stable/c/b9433b25cb06c415c9cb24782599649a406c8d6d |
| https://git.kernel.org/stable/c/5761eb9761d2d5fe8248a9b719efc4d8baf1f24a |
