All vulnerabilities
CVE-2026-93251

Linux: ACPI: bus: Introduce acpi_bus_get_primary_device()

Linux LinuxOperating systems
CVSS
NoneNot scored
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.20%Chance of exploitation activity in the next 30 days, higher than 9% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in50ddd82b88b1d1cc467b5df953344c1a9feec268Also 5657859851abb65105220a6cdb5804926249f714, 72530e1f72b0515a73fd88292254d04fecf03649CVE List
Published24 Sep 2026Updated 21 Oct 2026CVE List

What fixes it

  • 50ddd82b88b1d1cc467b5df953344c1a9feec268LinuxCVE List
  • 5657859851abb65105220a6cdb5804926249f714LinuxCVE List
  • 72530e1f72b0515a73fd88292254d04fecf03649LinuxCVE List

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

In the Linux kernel, the following vulnerability has been resolved:

ACPI: bus: Introduce acpi_bus_get_primary_device()

The function used for obtaining the first "physical" device for which the given ACPI one is the ACPI companion, acpi_get_first_physical_node(), may return a stale device pointer (mostly in theory) because acpi_unbind_one() may run as a whole after dropping the ACPI device's physical_node_lock in acpi_get_first_physical_node() and before it returns. The last reference to the "physical" device may be dropped then before the pointer to it is returned to the caller.

If that happens and the acpi_get_first_physical_node() caller invokes get_device() on the pointer obtained from it, which is done by the majority of its callers, a use-after-free will occur.

To prepare for addressing this problem, introduce a new function for getting the first "physical" device associated with the given ACPI one (the "primary physical device") that will also reference count the device in question before returning a pointer to it.

Make that new function and acpi_get_first_physical_node() share the physical node list lookup code.

No intentional functional impact.

Text from CVE List

Affected versions 12

  • Linuxaffected: 91e5687805885f9fceb60b95e950a3d3bdcf4764 before 50ddd82b88b1d1cc467b5df953344c1a9feec268CVE List
  • Linuxaffected: 91e5687805885f9fceb60b95e950a3d3bdcf4764 before fd4f907b558721716da30acd6630191acf811b95CVE List
  • Linuxaffected: 91e5687805885f9fceb60b95e950a3d3bdcf4764 before ebdd932dc24c1cf7cc31710b7730515e4e66d886CVE List
  • Linuxaffected: 91e5687805885f9fceb60b95e950a3d3bdcf4764 before 5657859851abb65105220a6cdb5804926249f714CVE List
  • Linuxaffected: 91e5687805885f9fceb60b95e950a3d3bdcf4764 before 72530e1f72b0515a73fd88292254d04fecf03649CVE List
  • Linuxaffected: 3.8CVE List
  • Linuxunaffected: all versions before 3.8CVE List
  • Linuxunaffected: 6.6.160 through 6.6.*CVE List
  • Linuxunaffected: 6.12.114 through 6.12.*CVE List
  • Linuxunaffected: 6.18.57 through 6.18.*CVE List
  • Linuxunaffected: 7.2.6 through 7.2.*CVE List
  • Linuxunaffected: 7.3CVE List

References 5