# CVE-2026-93143: staging: media: ipu7: fix pm_runtime refcount leak in ipu7_resume()

> A resource leak in the Linux kernel IPU7 driver allows local attackers to cause a denial of service by exhausting runtime PM references.

- **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:** BELL-CVE-2026-93143, DEBIAN-CVE-2026-93143, GHSA-f9hr-9g5j-m6mm, UBUNTU-CVE-2026-93143

## What is CVE-2026-93143?

CVE-2026-93143 is a denial of service 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:

staging: media: ipu7: fix pm_runtime refcount leak in ipu7_resume()

ipu7_resume() calls pm_runtime_get_sync() before resuming the device.
If the runtime PM resume fails, the usage count remains incremented, but
the error path returns without dropping the reference.

Use pm_runtime_resume_and_get() instead, which balances the usage count
on failure and avoids the leak. Keep returning 0 on error, as resume
callbacks should not propagate failures to the PM core, matching the
behaviour of the ipu6 driver.

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


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

Apply the vendor's patch.

## Is CVE-2026-93143 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93143 is a denial of service 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-93143 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-93143/ (Markdown: https://insights.sbomify.com/CVE-2026-93143/index.md)
```

## Sources

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

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