CVE-2026-99150

Reference-count corruption via double runtime-PM decrement

Published Oct 28, 2026 · Updated Oct 28, 2026

Reference-count corruption in Linux amdgpu allows local users to underflow the runtime-PM counter via a faulty debugfs read. In amdgpu_debugfs_gpr_read(), a failed put_user() jumps to cleanup that releases a runtime-PM reference already released after register access. Triggering requires access to amdgpu_gpr and an invalid destination buffer; the interface is owner-readable and disabled by kernel lockdown, and the documented consequence on Navi31 is loss of another holder's reference or counter underflow, not a demonstrated crash.

CVSS severityUnavailable
Unscored
EPSS probability0.18%
Next 30 days · Nov 1, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

Summary

What happened

Reference-count corruption in Linux amdgpu allows local users to underflow the runtime-PM counter via a faulty debugfs read. In amdgpu_debugfs_gpr_read(), a failed put_user() jumps to cleanup that releases a runtime-PM reference already released after register access. Triggering requires access to amdgpu_gpr and an invalid destination buffer; the interface is owner-readable and disabled by kernel lockdown, and the documented consequence on Navi31 is loss of another holder's reference or counter underflow, not a demonstrated crash.

The record

CVE
CVE-2026-99150
Published
Oct 28, 2026
Updated
Oct 28, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Oct 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.8.2 <5.9
  2. Affected versionversion=5.9
  3. Affected versionversion=865e2dbadf6856c9219626fbd6154cac44e5fbca
  4. Affected versionversion=9eee152aab56d374edb9ad21b3db05f5cdda2fe6 <253555a9baccefffe1f6e5f2fe54363c7c01ebb9
  5. Affected versionversion=9eee152aab56d374edb9ad21b3db05f5cdda2fe6 <652b1f26125fe48aed5f4944698a85b457eef491
  6. Affected versionversion=9eee152aab56d374edb9ad21b3db05f5cdda2fe6 <de9f6bcdb44f0e410031002e2f103826ea6b6259

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

The Linux Kernel Organization · Linuxversion=5.8.2 <5.9; version=5.9; version=865e2dbadf6856c9219626fbd6154cac44e5fbca; version=9eee152aab56d374edb9ad21b3db05f5cdda2fe6 <253555a9baccefffe1f6e5f2fe54363c7c01ebb9; version=9eee152aab56d374edb9ad21b3db05f5cdda2fe6 <652b1f26125fe48aed5f4944698a85b457eef491; version=9eee152aab56d374edb9ad21b3db05f5cdda2fe6 <de9f6bcdb44f0e410031002e2f103826ea6b6259

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us