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-90194ACPI: scan: fix bus ID cleanup on device_add() failures

Description

In the Linux kernel, the following vulnerability has been resolved: ACPI: scan: fix bus ID cleanup on device_add() failures When device_add() fails after acpi_device_set_name() has allocated an instance ID and a new acpi_device_bus_id has been linked into acpi_bus_id_list, the rollback path only removes wakeup_list and detaches the ACPI handle data. That leaves the bus-ID bookkeeping behind and keeps the allocated instance number consumed. Move the bus-ID cleanup and wakeup-list removal into a single helper. Use it from both the normal device teardown path and the device_add() rollback path. The wakeup list node is initialized before registration, so it can be deleted without checking whether the device is wakeup- capable like in the original teardown path. [ rjw: Rename acpi_device_del_list() to acpi_device_cleanup() ] [ rjw: Subject and changelog edits ]

Timeline

  1. ID reserved

    By Linux

  2. · 6 days 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.21% · top 89% of all CVEs (16 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 d783156ea38431b20af0d4f910a6f9f9054d33b9 – < 8cc2017aa804f157e717b5fd471e50fbddfec654
    • affected d783156ea38431b20af0d4f910a6f9f9054d33b9 – < f30379b8a4e24623594235dd5aefb2957e0cc228
    • affected d783156ea38431b20af0d4f910a6f9f9054d33b9 – < 83ee65feadc88de681abc6e977d54eceda95abd7
    • affected d783156ea38431b20af0d4f910a6f9f9054d33b9 – < 15512c6b5dea72fb5f1f41c1aa96f3f32531ca03
    • affected d783156ea38431b20af0d4f910a6f9f9054d33b9 – < 0b9053cd0955c7cd66d71a8442be33926d70e197
    • affected d783156ea38431b20af0d4f910a6f9f9054d33b9 – < a414485ebc2aa50907d0ce97cde2b1a353696897
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • 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

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .