CVE-2026-92521

ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root

N/A
Published: September 17, 2026 at 04:10 PM UTC
Updated: October 19, 2026 at 10:16 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.28db89b4f0dbab837d0f3de2c3e9427a8d5393afa3
Vendor states this is fixed in 321bb0eb1486a0d575f02e24e3f4170e408c2f51 (fixed)
Vendor states this is fixed in 3c1e8a14f9d06c1ed6f3e4bd2d283a62079109e2 (fixed)
Vendor states this is fixed in 3eee4c21931dc048ce63b86809f04e4e6f0dcad5 (fixed)
Vendor states this is fixed in 6aaf6dbf54fdfae096f3f90a79e9614e46579280 (fixed)
Vendor states this is fixed in 6e11ac626f9f9fc3a2ed27dfa44ccbe5fb762217 (fixed)
Vendor states this is fixed in 70cf773cca30a10b4964c24520a71279c974b899 (fixed)
Vendor states this is fixed in 8a742141f7ab84975aa758b775567ef4740ef0cf (fixed)
Vendor states this is fixed in a285fa3780c768dcc51c76768707d099a2cc611d (fixed)
Vendor states this is fixed in 2.6.28 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card