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

> A memory leak in the Linux kernel ACPI scan module can lead to resource exhaustion and denial of service when device addition fails.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102036, BELL-CVE-2026-90194, DEBIAN-CVE-2026-90194, GHSA-37ww-vf7x-2832, UBUNTU-CVE-2026-90194

## What is CVE-2026-90194?

CVE-2026-90194 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-90194?


## How do I fix CVE-2026-90194?

Apply the vendor's patch.

## Is CVE-2026-90194 being exploited?

There is no known exploitation of CVE-2026-90194 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90194 and fix it if it is affected.

What it is: CVE-2026-90194 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90194 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90194/ (Markdown: https://insights.sbomify.com/CVE-2026-90194/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90194
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90194
- OSV: https://osv.dev/vulnerability/CVE-2026-90194

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90194/
Summaries are generated and may contain mistakes; the official description above is the record.