| 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-49823: ata: libata-transport: fix error handling in ata_tdev_add() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ata: libata-transport: fix error handling in ata_tdev_add() |
| |
| In ata_tdev_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: 13 PID: 13603 Comm: rmmod Kdump: loaded Tainted: G W 6.1.0-rc3+ #36 |
| pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) |
| pc : device_del+0x48/0x3a0 |
| lr : device_del+0x44/0x3a0 |
| Call trace: |
| device_del+0x48/0x3a0 |
| attribute_container_class_device_del+0x28/0x40 |
| transport_remove_classdev+0x60/0x7c |
| attribute_container_device_trigger+0x118/0x120 |
| transport_remove_device+0x20/0x30 |
| ata_tdev_delete+0x24/0x50 [libata] |
| ata_tlink_delete+0x40/0xa0 [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_tdev_add(). In the error path, device_del() is called to delete |
| the device which was added earlier in this function, and ata_tdev_free() |
| is called to free ata_dev. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49823 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 5.10.156 with commit ef2ac07ab83163b9a53f45da20e14302591ad9cc |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 5.15.80 with commit f23058dc2398db1d8faca9a2b1ce30b85cdd8b22 |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 6.0.10 with commit f54331962883f4fc4bf5e487e6e7cf07c4567fef |
| Issue introduced in 2.6.37 with commit d9027470b88631d0956ac37cdadfdeb9cdcf2c99 and fixed in 6.1 with commit 1ff36351309e3eadcff297480baf4785e726de9b |
| |
| 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-49823 |
| 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/ef2ac07ab83163b9a53f45da20e14302591ad9cc |
| https://git.kernel.org/stable/c/f23058dc2398db1d8faca9a2b1ce30b85cdd8b22 |
| https://git.kernel.org/stable/c/f54331962883f4fc4bf5e487e6e7cf07c4567fef |
| https://git.kernel.org/stable/c/1ff36351309e3eadcff297480baf4785e726de9b |
