ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root acpi_pci_root_add() assigns the freshly allocated root to device->driver_data before dmar_device_add() and pci_acpi_scan_root(). Both failure paths reach the end: label where root is kfree()'d, but only the pci_acpi_scan_root() path clears driver_data first. When dmar_device_add() fails during a hot-add, root is freed while device->driver_data still points at it. The ACPI core does not clear driver_data on attach failure, so a later acpi_pci_find_root() call may dereference this dangling pointer. acpi_pci_root_remove() has the same problem: it frees root without clearing device->driver_data, leaving a dangling pointer behind after the root bridge is removed. Move the NULL assignment to the shared end: label so every error path in acpi_pci_root_add() clears driver_data before freeing root, and clear it in acpi_pci_root_remove() as well, so the object is never left reachable through driver_data after being freed.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in 321bb0eb1486a0d575f02e24e3f4170e408c2f51; From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in 3c1e8a14f9d06c1ed6f3e4bd2d283a62079109e2; From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in a285fa3780c768dcc51c76768707d099a2cc611d; From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in 6aaf6dbf54fdfae096f3f90a79e9614e46579280; From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in 70cf773cca30a10b4964c24520a71279c974b899; From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in 3eee4c21931dc048ce63b86809f04e4e6f0dcad5; From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in 6e11ac626f9f9fc3a2ed27dfa44ccbe5fb762217; From db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 · fixed in 8a742141f7ab84975aa758b775567ef4740ef0cf
- Linux Linux
2.6.28
- KernelLinux
From 2.6.28 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/321bb0eb1486a0d575f02e24e3f4170e408c2f51
- stable/c/3c1e8a14f9d06c1ed6f3e4bd2d283a62079109e2
- stable/c/a285fa3780c768dcc51c76768707d099a2cc611d
- stable/c/6aaf6dbf54fdfae096f3f90a79e9614e46579280
- stable/c/70cf773cca30a10b4964c24520a71279c974b899
- stable/c/3eee4c21931dc048ce63b86809f04e4e6f0dcad5
- stable/c/6e11ac626f9f9fc3a2ed27dfa44ccbe5fb762217
- stable/c/8a742141f7ab84975aa758b775567ef4740ef0cf