# CVE-2026-98513: drm/nouveau: Fix runtime PM leak in nouveau_connector_detect()

> A resource leak in the nouveau driver can keep the GPU powered on indefinitely, potentially causing battery drain or thermal issues.

- **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-98513, DEBIAN-CVE-2026-98513, GHSA-fc6c-gr57-5x28, UBUNTU-CVE-2026-98513

## What is CVE-2026-98513?

CVE-2026-98513 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:

drm/nouveau: Fix runtime PM leak in nouveau_connector_detect()

If nvif_outp_edid_get() fails, nouveau_connector_detect() returns
early without dropping the runtime PM reference taken at the start
of the function, keeping the device powered on until the next
successful detect.

Balance the reference on the error path like the other exit paths
do.

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


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

Apply the vendor's patch.

## Is CVE-2026-98513 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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