platform/surface: acpi-notify: Check ACPI companion before use
Summary
| CVE | CVE-2026-93114 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:18:05 UTC |
| Updated | 2026-10-19 10:17:01 UTC |
| 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. |
Risk And Classification
EPSS: 0.001720000 probability, percentile 0.069780000 (date 2026-09-18)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected a9e10e58730432e5de840eb3ddd55c75f29341b3 4faa43d4ef0b98beb6c2b77a279f4aa5d7fa2d13 git | Not specified |
| CNA | Linux | Linux | affected a9e10e58730432e5de840eb3ddd55c75f29341b3 3855be0100efb98c26228c610db70a673611f3bd git | Not specified |
| CNA | Linux | Linux | affected a9e10e58730432e5de840eb3ddd55c75f29341b3 f276b62f2ce1cbff7fa50a8ee5afd8fef5a60897 git | Not specified |
| CNA | Linux | Linux | affected a9e10e58730432e5de840eb3ddd55c75f29341b3 9b6479da662c2ec4e931ed9f7228df46aa8c3766 git | Not specified |
| CNA | Linux | Linux | affected a9e10e58730432e5de840eb3ddd55c75f29341b3 7fea5a310e3b2db24f7aafe64897e4e659ffbb7d git | Not specified |
| CNA | Linux | Linux | affected a9e10e58730432e5de840eb3ddd55c75f29341b3 428a82d987fcd8844e8868c85582eae75b4b5c51 git | Not specified |
| CNA | Linux | Linux | affected a9e10e58730432e5de840eb3ddd55c75f29341b3 2b3a5dabe89e330413af403246b648c1890f368f git | Not specified |
| CNA | Linux | Linux | affected 5.14 | Not specified |
| CNA | Linux | Linux | unaffected 5.14 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.221 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.188 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.157 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.110 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.52 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.6 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/3855be0100efb98c26228c610db70a673611f3bd | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2b3a5dabe89e330413af403246b648c1890f368f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4faa43d4ef0b98beb6c2b77a279f4aa5d7fa2d13 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/428a82d987fcd8844e8868c85582eae75b4b5c51 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/9b6479da662c2ec4e931ed9f7228df46aa8c3766 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7fea5a310e3b2db24f7aafe64897e4e659ffbb7d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f276b62f2ce1cbff7fa50a8ee5afd8fef5a60897 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.