| From bippy-1.1.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-53056: scsi: qla2xxx: Synchronize the IOCB count to be in order |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: qla2xxx: Synchronize the IOCB count to be in order |
| |
| A system hang was observed with the following call trace: |
| |
| BUG: kernel NULL pointer dereference, address: 0000000000000000 |
| PGD 0 P4D 0 |
| Oops: 0000 [#1] PREEMPT SMP NOPTI |
| CPU: 15 PID: 86747 Comm: nvme Kdump: loaded Not tainted 6.2.0+ #1 |
| Hardware name: Dell Inc. PowerEdge R6515/04F3CJ, BIOS 2.7.3 03/31/2022 |
| RIP: 0010:__wake_up_common+0x55/0x190 |
| Code: 41 f6 01 04 0f 85 b2 00 00 00 48 8b 43 08 4c 8d |
| 40 e8 48 8d 43 08 48 89 04 24 48 89 c6\ |
| 49 8d 40 18 48 39 c6 0f 84 e9 00 00 00 <49> 8b 40 18 89 6c 24 14 31 |
| ed 4c 8d 60 e8 41 8b 18 f6 c3 04 75 5d |
| RSP: 0018:ffffb05a82afbba0 EFLAGS: 00010082 |
| RAX: 0000000000000000 RBX: ffff8f9b83a00018 RCX: 0000000000000000 |
| RDX: 0000000000000001 RSI: ffff8f9b83a00020 RDI: ffff8f9b83a00018 |
| RBP: 0000000000000001 R08: ffffffffffffffe8 R09: ffffb05a82afbbf8 |
| R10: 70735f7472617473 R11: 5f30307832616c71 R12: 0000000000000001 |
| R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 |
| FS: 00007f815cf4c740(0000) GS:ffff8f9eeed80000(0000) |
| knlGS:0000000000000000 |
| CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 |
| CR2: 0000000000000000 CR3: 000000010633a000 CR4: 0000000000350ee0 |
| Call Trace: |
| <TASK> |
| __wake_up_common_lock+0x83/0xd0 |
| qla_nvme_ls_req+0x21b/0x2b0 [qla2xxx] |
| __nvme_fc_send_ls_req+0x1b5/0x350 [nvme_fc] |
| nvme_fc_xmt_disconnect_assoc+0xca/0x110 [nvme_fc] |
| nvme_fc_delete_association+0x1bf/0x220 [nvme_fc] |
| ? nvme_remove_namespaces+0x9f/0x140 [nvme_core] |
| nvme_do_delete_ctrl+0x5b/0xa0 [nvme_core] |
| nvme_sysfs_delete+0x5f/0x70 [nvme_core] |
| kernfs_fop_write_iter+0x12b/0x1c0 |
| vfs_write+0x2a3/0x3b0 |
| ksys_write+0x5f/0xe0 |
| do_syscall_64+0x5c/0x90 |
| ? syscall_exit_work+0x103/0x130 |
| ? syscall_exit_to_user_mode+0x12/0x30 |
| ? do_syscall_64+0x69/0x90 |
| ? exit_to_user_mode_loop+0xd0/0x130 |
| ? exit_to_user_mode_prepare+0xec/0x100 |
| ? syscall_exit_to_user_mode+0x12/0x30 |
| ? do_syscall_64+0x69/0x90 |
| ? syscall_exit_to_user_mode+0x12/0x30 |
| ? do_syscall_64+0x69/0x90 |
| entry_SYSCALL_64_after_hwframe+0x72/0xdc |
| RIP: 0033:0x7f815cd3eb97 |
| |
| The IOCB counts are out of order and that would block any commands from |
| going out and subsequently hang the system. Synchronize the IOCB count to |
| be in correct order. |
| |
| The Linux kernel CVE team has assigned CVE-2023-53056 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.15.99 with commit d58b45bbbea8f9516b66e0b494701c369adb0ae8 and fixed in 5.15.105 with commit 6295b3ec64a3623fa96869ffb7cf17d0b3c92035 |
| Issue introduced in 6.1.16 with commit 6626b7494a01561fe5151fa6976875014a343a14 and fixed in 6.1.22 with commit 6d57b77d7369ed73836c82b25f785b34923eef84 |
| Issue introduced in 6.2.3 with commit f2dde125ae9849b84f46a98abd98f655148821ab and fixed in 6.2.9 with commit ffd7831841d3c56c655531fc8c5acafaaf20e1bb |
| |
| 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-2023-53056 |
| 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/qla2xxx/qla_isr.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/6295b3ec64a3623fa96869ffb7cf17d0b3c92035 |
| https://git.kernel.org/stable/c/6d57b77d7369ed73836c82b25f785b34923eef84 |
| https://git.kernel.org/stable/c/ffd7831841d3c56c655531fc8c5acafaaf20e1bb |
| https://git.kernel.org/stable/c/d3affdeb400f3adc925bd996f3839481f5291839 |
