CVE-2026-99150drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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)
Timeline
ID reserved
By Linux
- 33 days later
· 33 days later
Published
- 2 days later
· 2 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < 24c1f6e381d564e5f6893323cfe0264950358451
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < c333834b1b9cbb1021c954d29fa2373ac9e73499
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < eda6b57a83d942199a5947e73556fe918affad86
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < f9c0b333a5e44f734478ca8a7345f8b87d65ba7c
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < 35aa048f242cade635f17924183c1df0ffe7a486
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < 652b1f26125fe48aed5f4944698a85b457eef491
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < 253555a9baccefffe1f6e5f2fe54363c7c01ebb9
- affected 9eee152aab56d374edb9ad21b3db05f5cdda2fe6 – < de9f6bcdb44f0e410031002e2f103826ea6b6259
- affected 865e2dbadf6856c9219626fbd6154cac44e5fbca
- affected 5.8.2 – < 5.9
- affected 5.9
- unaffected < 5.9
- unaffected 5.10.273 – ≤ 5.10.*
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.161 – ≤ 6.6.*
- unaffected 6.12.115 – ≤ 6.12.*
- unaffected 6.18.59 – ≤ 6.18.*
- unaffected 7.2.13 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/24c1f6e381d564e5f6893323cfe0264950358451 (opens in a new tab)
- https://git.kernel.org/stable/c/c333834b1b9cbb1021c954d29fa2373ac9e73499 (opens in a new tab)
- https://git.kernel.org/stable/c/eda6b57a83d942199a5947e73556fe918affad86 (opens in a new tab)
- https://git.kernel.org/stable/c/f9c0b333a5e44f734478ca8a7345f8b87d65ba7c (opens in a new tab)
- https://git.kernel.org/stable/c/35aa048f242cade635f17924183c1df0ffe7a486 (opens in a new tab)
- https://git.kernel.org/stable/c/652b1f26125fe48aed5f4944698a85b457eef491 (opens in a new tab)
- https://git.kernel.org/stable/c/253555a9baccefffe1f6e5f2fe54363c7c01ebb9 (opens in a new tab)
- https://git.kernel.org/stable/c/de9f6bcdb44f0e410031002e2f103826ea6b6259 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-111902 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99150)Record last updated .