Menu

Star on GitHub · 3.5k

CVE-2026-93251

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 gi…

Published Sep 24, 2026EPSS 0.21%

Overview

CVE-2026-93251 is a known-severity vulnerability. It was published on September 24, 2026.

Technical 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 q

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-93251?

CVE-2026-93251 is a known-severity vulnerability. It was published on September 24, 2026.

How severe is CVE-2026-93251?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-93251?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-93251?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-93251 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach