Strix
64.2K

CVE-2026-90194

Unknown

Last modified

CVE-2026-90194 is a vulnerability of currently unknown severity. 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 ].

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= d783156ea38431b20af0d4f910a6f9f9054d33b9, < 8cc2017aa804f157e717b5fd471e50fbddfec654; >= d783156ea38431b20af0d4f910a6f9f9054d33b9, < f30379b8a4e24623594235dd5aefb2957e0cc228; >= d783156ea38431b20af0d4f910a6f9f9054d33b9, < 83ee65feadc88de681abc6e977d54eceda95abd7; >= d783156ea38431b20af0d4f910a6f9f9054d33b9, < 15512c6b5dea72fb5f1f41c1aa96f3f32531ca03; >= d783156ea38431b20af0d4f910a6f9f9054d33b9, < 0b9053cd0955c7cd66d71a8442be33926d70e197; >= d783156ea38431b20af0d4f910a6f9f9054d33b9, < a414485ebc2aa50907d0ce97cde2b1a353696897
LinuxLinux3.14

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-90194?
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 ]
How severe is CVE-2026-90194?
Severity scoring for CVE-2026-90194 is pending analysis.
How do I fix CVE-2026-90194?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-90194?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST