# CVE-2026-99150: drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111281, BELL-CVE-2026-99150, DEBIAN-CVE-2026-99150, GHSA-9m2r-pjhq-4578, UBUNTU-CVE-2026-99150

## What is CVE-2026-99150?

CVE-2026-99150 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr

amdgpu_debugfs_gpr_read() drops its runtime PM reference right after
reading the wave registers. When copying them to userspace fails, it
jumps to the err label, which drops the reference a second time. A read
into a bad buffer on Navi31 either steals a reference somebody else
holds (power/runtime_usage goes from 1 to 0) or underflows the count:

  amdgpu 0000:03:00.0: Runtime PM usage count underflow!

The registers are already in the kernel buffer at that point, so finish
the hardware access first and copy the buffer with a single
copy_to_user() instead of the put_user() loop with its own error path.

(cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)

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


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

Upgrade to a fixed version.

## Is CVE-2026-99150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99150 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99150 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-99150/ (Markdown: https://insights.sbomify.com/CVE-2026-99150/index.md)
```

## Sources

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

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