# CVE-2026-89869: media: qcom: iris: use disable_irq() during power-off

> A race condition in the Qualcomm Iris VPU driver allows hardware register access after power-off, potentially causing system instability or denial of service.

- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89869, DEBIAN-CVE-2026-89869, GHSA-5mhw-wrx9-mqjj, UBUNTU-CVE-2026-89869

## What is CVE-2026-89869?

CVE-2026-89869 is a vulnerability in Linux, published on 16 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:

media: qcom: iris: use disable_irq() during power-off

The IRQ is registered as a threaded IRQ.

Using disable_irq_nosync() in iris_vpu_power_off() does not wait
for an already queued threaded IRQ handler to complete before
returning.

As a result, a threaded IRQ handler may still run after the VPU has
been powered down and access hardware registers after power-off.

Replace disable_irq_nosync() with disable_irq() so the power-off path
waits for any in-flight threaded IRQ handler to complete before
returning.

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


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

Apply the vendor's patch.

## Is CVE-2026-89869 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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