# CVE-2026-89446: iommufd: Release current IOAS on xa_store() failure

> A local attacker can cause a resource leak in the Linux kernel iommufd subsystem by triggering a specific error path, leading to potential denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89446, DEBIAN-CVE-2026-89446, GHSA-9fjc-q922-2qfq, UBUNTU-CVE-2026-89446

## What is CVE-2026-89446?

CVE-2026-89446 is a denial of service vulnerability in Linux, published on 11 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:

iommufd: Release current IOAS on xa_store() failure

iommufd_take_all_iova_rwsem() takes an object reference and the
iova_rwsem write lock before storing the IOAS in the temporary ioas_list
xarray.

If xa_store() fails, the current IOAS has not been inserted into
ioas_list yet. iommufd_release_all_iova_rwsem() only unwinds IOAS
objects already present in that xarray, so it cannot release the current
IOAS.

Release the current IOAS rwsem and object reference before unwinding the
previously stored entries.

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


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

Apply the vendor's patch.

## Is CVE-2026-89446 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89446 is a denial of service vulnerability in Linux, published on 11 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-89446 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-89446/ (Markdown: https://insights.sbomify.com/CVE-2026-89446/index.md)
```

## Sources

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

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