VulnerabilityPublished 28 Oct 2026

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

Source GCVE Database

Authoritative record:CVE-2026-99150

Not known to be exploited · fixed in de9f6bcdb44f0e410031002e2f103826ea6b6259 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 14:02 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in de9f6bcdb44f0e410031002e2f103826ea6b6259, 253555a9baccefffe1f6e5f2fe54363c7c01ebb9, 652b1f26125fe48aed5f4944698a85b457eef491 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-9m2r-pjhq-4578

What to do

Upgrade Linux to de9f6bcdb44f0e410031002e2f103826ea6b6259, 253555a9baccefffe1f6e5f2fe54363c7c01ebb9, 652b1f26125fe48aed5f4944698a85b457eef491 or 5.9; the Debian debian/linux package to 5.9.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=5.8.2 <5.9	Fixed in de9f6bcdb44f0e410031002e2f103826ea6b6259 253555a9baccefffe1f6e5f2fe54363c7c01ebb9 652b1f26125fe48aed5f4944698a85b457eef491 5.9
LinuxLinux	Affected =5.9	Fixed in–
Debiandebian/linux`pkg:deb/debian/linux`Other threats	Affected >=5.8.2 <5.9 =5.9	Fixed in 5.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been applied in the Linux kernel to address this issue by correcting the runtime PM reference handling in the amdgpu driver. Users should update to a kernel version that includes this patch. Since this is a kernel-level fix, applying the official kernel update is the recommended mitigation.

Description

A vulnerability in the Linux kernel's AMDGPU driver involves improper handling of runtime power management references in the amdgpu_gpr function. Specifically, the runtime PM reference is dropped twice when copying wave register data to userspace fails, leading to a runtime PM usage count underflow. This issue affects the amdgpu_debugfs_gpr_read() function and can cause incorrect power management state accounting on affected hardware.

References

Community reviews

Loading reviews…