| 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-2022-49217: scsi: pm8001: Fix abort all task initialization |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: pm8001: Fix abort all task initialization |
| |
| In pm80xx_send_abort_all(), the n_elem field of the ccb used is not |
| initialized to 0. This missing initialization sometimes lead to the task |
| completion path seeing the ccb with a non-zero n_elem resulting in the |
| execution of invalid dma_unmap_sg() calls in pm8001_ccb_task_free(), |
| causing a crash such as: |
| |
| [ 197.676341] RIP: 0010:iommu_dma_unmap_sg+0x6d/0x280 |
| [ 197.700204] RSP: 0018:ffff889bbcf89c88 EFLAGS: 00010012 |
| [ 197.705485] RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff83d0bda0 |
| [ 197.712687] RDX: 0000000000000002 RSI: 0000000000000000 RDI: ffff88810dffc0d0 |
| [ 197.719887] RBP: 0000000000000000 R08: 0000000000000000 R09: ffff8881c790098b |
| [ 197.727089] R10: ffffed1038f20131 R11: 0000000000000001 R12: 0000000000000000 |
| [ 197.734296] R13: ffff88810dffc0d0 R14: 0000000000000010 R15: 0000000000000000 |
| [ 197.741493] FS: 0000000000000000(0000) GS:ffff889bbcf80000(0000) knlGS:0000000000000000 |
| [ 197.749659] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 |
| [ 197.755459] CR2: 00007f16c1b42734 CR3: 0000000004814000 CR4: 0000000000350ee0 |
| [ 197.762656] Call Trace: |
| [ 197.765127] <IRQ> |
| [ 197.767162] pm8001_ccb_task_free+0x5f1/0x820 [pm80xx] |
| [ 197.772364] ? do_raw_spin_unlock+0x54/0x220 |
| [ 197.776680] pm8001_mpi_task_abort_resp+0x2ce/0x4f0 [pm80xx] |
| [ 197.782406] process_oq+0xe85/0x7890 [pm80xx] |
| [ 197.786817] ? lock_acquire+0x194/0x490 |
| [ 197.790697] ? handle_irq_event+0x10e/0x1b0 |
| [ 197.794920] ? mpi_sata_completion+0x2d70/0x2d70 [pm80xx] |
| [ 197.800378] ? __wake_up_bit+0x100/0x100 |
| [ 197.804340] ? lock_is_held_type+0x98/0x110 |
| [ 197.808565] pm80xx_chip_isr+0x94/0x130 [pm80xx] |
| [ 197.813243] tasklet_action_common.constprop.0+0x24b/0x2f0 |
| [ 197.818785] __do_softirq+0x1b5/0x82d |
| [ 197.822485] ? do_raw_spin_unlock+0x54/0x220 |
| [ 197.826799] __irq_exit_rcu+0x17e/0x1e0 |
| [ 197.830678] irq_exit_rcu+0xa/0x20 |
| [ 197.834114] common_interrupt+0x78/0x90 |
| [ 197.840051] </IRQ> |
| [ 197.844236] <TASK> |
| [ 197.848397] asm_common_interrupt+0x1e/0x40 |
| |
| Avoid this issue by always initializing the ccb n_elem field to 0 in |
| pm8001_send_abort_all(), pm8001_send_read_log() and |
| pm80xx_send_abort_all(). |
| |
| The Linux kernel CVE team has assigned CVE-2022-49217 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 4.9.311 with commit 9914461db82caee6c519acfbe10a86fe11bcdeca |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 4.14.276 with commit d6ec4471550cc53e96485a7124c5891e6a38d1c3 |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 4.19.238 with commit 1824a21b2cedc5774a5adfa74f5f7b90472d8677 |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 5.4.189 with commit 765674e3b30121782a2b792684554baa48c61f5e |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 5.10.110 with commit 279f318bd7d6e04e6e0bc7b8cd8e190da8fa37a4 |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 5.15.33 with commit c8db786858d895ac58342f67767b4999ae6538fa |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 5.16.19 with commit 326d894adf89f3c707b7784becbe241830daaab6 |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 5.17.2 with commit 16cd02e0951b520bef324adb9a35afcc92501caf |
| Issue introduced in 3.10 with commit c6b9ef5779c3e1edfa9de949d2a51252bc347663 and fixed in 5.18 with commit 7f12845c8389855dbcc67baa068b6832dc4a396e |
| |
| 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-2022-49217 |
| 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/pm8001/pm8001_hwi.c |
| drivers/scsi/pm8001/pm80xx_hwi.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/9914461db82caee6c519acfbe10a86fe11bcdeca |
| https://git.kernel.org/stable/c/d6ec4471550cc53e96485a7124c5891e6a38d1c3 |
| https://git.kernel.org/stable/c/1824a21b2cedc5774a5adfa74f5f7b90472d8677 |
| https://git.kernel.org/stable/c/765674e3b30121782a2b792684554baa48c61f5e |
| https://git.kernel.org/stable/c/279f318bd7d6e04e6e0bc7b8cd8e190da8fa37a4 |
| https://git.kernel.org/stable/c/c8db786858d895ac58342f67767b4999ae6538fa |
| https://git.kernel.org/stable/c/326d894adf89f3c707b7784becbe241830daaab6 |
| https://git.kernel.org/stable/c/16cd02e0951b520bef324adb9a35afcc92501caf |
| https://git.kernel.org/stable/c/7f12845c8389855dbcc67baa068b6832dc4a396e |
