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-93251ACPI: bus: Introduce acpi_bus_get_primary_device()

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 question before returning a pointer to it. Make that new function and acpi_get_first_physical_node() share the physical node list lookup code. No intentional functional impact.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 36 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.21% · top 88% of all CVEs (13 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 91e5687805885f9fceb60b95e950a3d3bdcf4764 – < f912f88126e385f6cfcd1a28de73afb7d3943c8d
    • affected 91e5687805885f9fceb60b95e950a3d3bdcf4764 – < 50ddd82b88b1d1cc467b5df953344c1a9feec268
    • affected 91e5687805885f9fceb60b95e950a3d3bdcf4764 – < fd4f907b558721716da30acd6630191acf811b95
    • affected 91e5687805885f9fceb60b95e950a3d3bdcf4764 – < ebdd932dc24c1cf7cc31710b7730515e4e66d886
    • affected 91e5687805885f9fceb60b95e950a3d3bdcf4764 – < 5657859851abb65105220a6cdb5804926249f714
    • affected 91e5687805885f9fceb60b95e950a3d3bdcf4764 – < 72530e1f72b0515a73fd88292254d04fecf03649
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .