| 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-2022-49839: scsi: scsi_transport_sas: Fix error handling in sas_phy_add() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| scsi: scsi_transport_sas: Fix error handling in sas_phy_add() |
| |
| If transport_add_device() fails in sas_phy_add(), the kernel will crash |
| trying to delete the device in transport_remove_device() called from |
| sas_remove_host(). |
| |
| Unable to handle kernel NULL pointer dereference at virtual address 0000000000000108 |
| CPU: 61 PID: 42829 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc1+ #173 |
| pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) |
| pc : device_del+0x54/0x3d0 |
| lr : device_del+0x37c/0x3d0 |
| Call trace: |
| device_del+0x54/0x3d0 |
| attribute_container_class_device_del+0x28/0x38 |
| transport_remove_classdev+0x6c/0x80 |
| attribute_container_device_trigger+0x108/0x110 |
| transport_remove_device+0x28/0x38 |
| sas_phy_delete+0x30/0x60 [scsi_transport_sas] |
| do_sas_phy_delete+0x6c/0x80 [scsi_transport_sas] |
| device_for_each_child+0x68/0xb0 |
| sas_remove_children+0x40/0x50 [scsi_transport_sas] |
| sas_remove_host+0x20/0x38 [scsi_transport_sas] |
| hisi_sas_remove+0x40/0x68 [hisi_sas_main] |
| hisi_sas_v2_remove+0x20/0x30 [hisi_sas_v2_hw] |
| platform_remove+0x2c/0x60 |
| |
| Fix this by checking and handling return value of transport_add_device() |
| in sas_phy_add(). |
| |
| The Linux kernel CVE team has assigned CVE-2022-49839 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.14 with commit c7ebbbce366c02e5657ac6b6059933fe0353b175 and fixed in 5.10.157 with commit 03aabcb88aeeb7221ddb6196ae84ad5fb17b743f |
| Issue introduced in 2.6.14 with commit c7ebbbce366c02e5657ac6b6059933fe0353b175 and fixed in 5.15.80 with commit 2f21d653c648735657e23948b1d7ac7273de0f87 |
| Issue introduced in 2.6.14 with commit c7ebbbce366c02e5657ac6b6059933fe0353b175 and fixed in 6.0.10 with commit c736876ee294bb4f271d76a25cc7d70c8537bc5d |
| Issue introduced in 2.6.14 with commit c7ebbbce366c02e5657ac6b6059933fe0353b175 and fixed in 6.1 with commit 5d7bebf2dfb0dc97aac1fbace0910e557ecdb16f |
| |
| 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-49839 |
| 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/scsi_transport_sas.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/03aabcb88aeeb7221ddb6196ae84ad5fb17b743f |
| https://git.kernel.org/stable/c/2f21d653c648735657e23948b1d7ac7273de0f87 |
| https://git.kernel.org/stable/c/c736876ee294bb4f271d76a25cc7d70c8537bc5d |
| https://git.kernel.org/stable/c/5d7bebf2dfb0dc97aac1fbace0910e557ecdb16f |
