CVE-2026-90194

ACPI: scan: fix bus ID cleanup on device_add() failures

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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 ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.14d783156ea38431b20af0d4f910a6f9f9054d33b9
Vendor states this is fixed in 0b9053cd0955c7cd66d71a8442be33926d70e197 (fixed)
Vendor states this is fixed in 15512c6b5dea72fb5f1f41c1aa96f3f32531ca03 (fixed)
Vendor states this is fixed in 83ee65feadc88de681abc6e977d54eceda95abd7 (fixed)
Vendor states this is fixed in 8cc2017aa804f157e717b5fd471e50fbddfec654 (fixed)
Vendor states this is fixed in a414485ebc2aa50907d0ce97cde2b1a353696897 (fixed)
Vendor states this is fixed in f30379b8a4e24623594235dd5aefb2957e0cc228 (fixed)
Vendor states this is fixed in 3.14 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card