| 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-49824: ata: libata-transport: fix error handling in ata_tlink_add() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ata: libata-transport: fix error handling in ata_tlink_add() |
| |
| In ata_tlink_add(), the return value of transport_add_device() is |
| not checked. As a result, it causes null-ptr-deref while removing |
| the module, because transport_remove_device() is called to remove |
| the device that was not added. |
| |
| Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0 |
| CPU: 33 PID: 13850 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #12 |
| pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) |
| pc : device_del+0x48/0x39c |
| lr : device_del+0x44/0x39c |
| Call trace: |
| device_del+0x48/0x39c |
| attribute_container_class_device_del+0x28/0x40 |
| transport_remove_classdev+0x60/0x7c |
| attribute_container_device_trigger+0x118/0x120 |
| transport_remove_device+0x20/0x30 |
| ata_tlink_delete+0x88/0xb0 [libata] |
| ata_tport_delete+0x2c/0x60 [libata] |
| ata_port_detach+0x148/0x1b0 [libata] |
| ata_pci_remove_one+0x50/0x80 [libata] |
| ahci_remove_one+0x4c/0x8c [ahci] |
| |
| Fix this by checking and handling return value of transport_add_device() |
| in ata_tlink_add(). |
| |
| The Linux kernel CVE team has assigned CVE-2022-49824 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 5.10.156 with commit 7377a14598f6b04446c54bc4a50cd249470d6c6f |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 5.15.80 with commit 67b219314628b90b3a314528e177335b0cd5c70b |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 6.0.10 with commit d5234480ca822bdcf03fe4d6a590ddcb854558f7 |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 6.1 with commit cf0816f6322c5c37ee52655f928e91ecf32da103 |
| |
| 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-49824 |
| 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/ata/libata-transport.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/7377a14598f6b04446c54bc4a50cd249470d6c6f |
| https://git.kernel.org/stable/c/67b219314628b90b3a314528e177335b0cd5c70b |
| https://git.kernel.org/stable/c/d5234480ca822bdcf03fe4d6a590ddcb854558f7 |
| https://git.kernel.org/stable/c/cf0816f6322c5c37ee52655f928e91ecf32da103 |
