VulnerabilityPublished 24 Sep 2026Updated 21 Oct 2026

CVE-2026-93251: Linux kernel · ACPI: bus: Introduce acpi_bus_get_primary_device()

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in fd4f907b558721716da30acd6630191acf811b95 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in fd4f907b558721716da30acd6630191acf811b95, ebdd932dc24c1cf7cc31710b7730515e4e66d886, 5657859851abb65105220a6cdb5804926249f714 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 91e5687805885f9fceb60b95e950a3d3bdcf4764, < fd4f907b558721716da30acd6630191acf811b95	Fixed in fd4f907b558721716da30acd6630191acf811b95
LinuxLinux	Affected ≥ 91e5687805885f9fceb60b95e950a3d3bdcf4764, < ebdd932dc24c1cf7cc31710b7730515e4e66d886	Fixed in ebdd932dc24c1cf7cc31710b7730515e4e66d886
LinuxLinux	Affected ≥ 91e5687805885f9fceb60b95e950a3d3bdcf4764, < 5657859851abb65105220a6cdb5804926249f714	Fixed in 5657859851abb65105220a6cdb5804926249f714
LinuxLinux	Affected ≥ 91e5687805885f9fceb60b95e950a3d3bdcf4764, < 72530e1f72b0515a73fd88292254d04fecf03649	Fixed in 72530e1f72b0515a73fd88292254d04fecf03649
LinuxLinux	Affected ≥ 91e5687805885f9fceb60b95e950a3d3bdcf4764, < 50ddd82b88b1d1cc467b5df953344c1a9feec268	Fixed in 50ddd82b88b1d1cc467b5df953344c1a9feec268
LinuxLinux	Affected =3.8	Fixed in–

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.

References

Community reviews

Loading reviews…