# CVE-2026-93114: platform/surface: acpi-notify: Check ACPI companion before use

> A local attacker with high privileges can force-bind a driver to a device lacking an ACPI companion, causing a kernel NULL pointer dereference and system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102186, BELL-CVE-2026-93114, DEBIAN-CVE-2026-93114, GHSA-fmfr-wc4p-75cj, UBUNTU-CVE-2026-93114

## What is CVE-2026-93114?

CVE-2026-93114 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-93114?


## How do I fix CVE-2026-93114?

Apply the vendor's patch.

## Is CVE-2026-93114 being exploited?

There is no known exploitation of CVE-2026-93114 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93114 and fix it if it is affected.

What it is: CVE-2026-93114 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93114 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93114/ (Markdown: https://insights.sbomify.com/CVE-2026-93114/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93114
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93114
- OSV: https://osv.dev/vulnerability/CVE-2026-93114

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93114/
Summaries are generated and may contain mistakes; the official description above is the record.