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-92521ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root

Description

In the Linux kernel, the following vulnerability has been resolved: ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root acpi_pci_root_add() assigns the freshly allocated root to device->driver_data before dmar_device_add() and pci_acpi_scan_root(). Both failure paths reach the end: label where root is kfree()'d, but only the pci_acpi_scan_root() path clears driver_data first. When dmar_device_add() fails during a hot-add, root is freed while device->driver_data still points at it. The ACPI core does not clear driver_data on attach failure, so a later acpi_pci_find_root() call may dereference this dangling pointer. acpi_pci_root_remove() has the same problem: it frees root without clearing device->driver_data, leaving a dangling pointer behind after the root bridge is removed. Move the NULL assignment to the shared end: label so every error path in acpi_pci_root_add() clears driver_data before freeing root, and clear it in acpi_pci_root_remove() as well, so the object is never left reachable through driver_data after being freed.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    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.18% · top 93% of all CVEs (18 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 db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < 321bb0eb1486a0d575f02e24e3f4170e408c2f51
    • affected db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < 3c1e8a14f9d06c1ed6f3e4bd2d283a62079109e2
    • affected db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < a285fa3780c768dcc51c76768707d099a2cc611d
    • affected db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < 6aaf6dbf54fdfae096f3f90a79e9614e46579280
    • affected db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < 70cf773cca30a10b4964c24520a71279c974b899
    • affected db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < 3eee4c21931dc048ce63b86809f04e4e6f0dcad5
    • affected db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < 6e11ac626f9f9fc3a2ed27dfa44ccbe5fb762217
    • affected db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 – < 8a742141f7ab84975aa758b775567ef4740ef0cf
  • Linux · Linux

    • affected 2.6.28
    • unaffected < 2.6.28
    • unaffected 5.10.270 – ≤ 5.10.*
    • 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

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .