# CVE-2026-98437: media: qcom: iris: fix runtime PM reference leaks

> A reference leak in the Qualcomm Iris media driver can cause resource exhaustion, leading to denial of service for local attackers.

- **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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98437, DEBIAN-CVE-2026-98437, GHSA-2w8w-fc6j-3f4v, UBUNTU-CVE-2026-98437

## What is CVE-2026-98437?

CVE-2026-98437 is a denial of service vulnerability in Linux, published on 18 Oct 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: fix runtime PM reference leaks

Use pm_runtime_resume_and_get() in iris_enable_power_domains()
to avoid leaking a runtime PM usage count on failure.

Also ensure pm_runtime_put_sync() is always called in
iris_disable_power_domains(), even when iris_opp_set_rate()
fails, so runtime PM references remain balanced.

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


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

Apply the vendor's patch.

## Is CVE-2026-98437 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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