CVE-2026-93114

platform/surface: acpi-notify: Check ACPI companion before use

N/A
Published: September 17, 2026 at 04:11 PM UTC
Updated: October 19, 2026 at 10:17 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: platform/surface: acpi-notify: Check ACPI companion before use Since every platform driver can be forced to match a device that doesn't match its list of device IDs because of device_match_driver_override(), platform drivers that rely on the existence of a device's ACPI companion object should verify its presence. san_probe() dereferences the result of ACPI_COMPANION() when installing the GSBUS address space handler, so force-binding the driver to a device without an ACPI companion leads to a NULL pointer dereference. The dereference was introduced when the probe function was switched from ACPI_HANDLE() to ACPI_COMPANION(). Check the ACPI companion against NULL and return -ENODEV when it is missing, like commit e4865a56d013 ("ACPI: driver: Check ACPI_COMPANION() against NULL during probe") does for the core ACPI platform drivers.

Affected

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

5.14a9e10e58730432e5de840eb3ddd55c75f29341b3
Vendor states this is fixed in 2b3a5dabe89e330413af403246b648c1890f368f (fixed)
Vendor states this is fixed in 3855be0100efb98c26228c610db70a673611f3bd (fixed)
Vendor states this is fixed in 428a82d987fcd8844e8868c85582eae75b4b5c51 (fixed)
Vendor states this is fixed in 4faa43d4ef0b98beb6c2b77a279f4aa5d7fa2d13 (fixed)
Vendor states this is fixed in 7fea5a310e3b2db24f7aafe64897e4e659ffbb7d (fixed)
Vendor states this is fixed in 9b6479da662c2ec4e931ed9f7228df46aa8c3766 (fixed)
Vendor states this is fixed in f276b62f2ce1cbff7fa50a8ee5afd8fef5a60897 (fixed)
Vendor states this is fixed in 5.14 (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