# CVE-2026-98519: drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()

> A local attacker can cause a GPU power management reference leak, keeping the GPU awake and potentially leading to resource exhaustion or 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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109298, BELL-CVE-2026-98519, DEBIAN-CVE-2026-98519, GHSA-6qmp-28g8-3p6v, UBUNTU-CVE-2026-98519

## What is CVE-2026-98519?

CVE-2026-98519 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/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()

amdgpu_debugfs_test_ib_show() resumes the device with
pm_runtime_get_sync() before taking the reset domain semaphore with
down_write_killable().  If the write lock acquisition is interrupted,
the function returns without calling pm_runtime_put_autosuspend(),
leaking the runtime PM reference acquired for the device and keeping
the GPU awake.

Drop the runtime PM reference on the interrupted down_write_killable()
error path before returning.

(cherry picked from commit ec30a576c2d4c0364549e6c04218f50704ef56c8)

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


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

Apply the vendor's patch.

## Is CVE-2026-98519 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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