Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected a9e10e58730432e5de840eb3ddd55c75f29341b3 – < 4faa43d4ef0b98beb6c2b77a279f4aa5d7fa2d13
    • affected a9e10e58730432e5de840eb3ddd55c75f29341b3 – < 3855be0100efb98c26228c610db70a673611f3bd
    • affected a9e10e58730432e5de840eb3ddd55c75f29341b3 – < f276b62f2ce1cbff7fa50a8ee5afd8fef5a60897
    • affected a9e10e58730432e5de840eb3ddd55c75f29341b3 – < 9b6479da662c2ec4e931ed9f7228df46aa8c3766
    • affected a9e10e58730432e5de840eb3ddd55c75f29341b3 – < 7fea5a310e3b2db24f7aafe64897e4e659ffbb7d
    • affected a9e10e58730432e5de840eb3ddd55c75f29341b3 – < 428a82d987fcd8844e8868c85582eae75b4b5c51
    • affected a9e10e58730432e5de840eb3ddd55c75f29341b3 – < 2b3a5dabe89e330413af403246b648c1890f368f
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93114 badge
[![CVE-2026-93114](https://cveledger.app/badge/CVE-2026-93114.svg)](https://cveledger.app/cve/CVE-2026-93114)

Record last updated .