Live › vulnerability › CVE-2026-98519
Go to dashboardIn the amdgpu graphics driver's debugfs test-IB show routine, an interrupted lock acquisition returns without dropping the runtime PM reference taken for the device. The GPU is then kept awake, which wastes power and blocks suspend, with no sign that an attacker gains code execution or data access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the amdgpu driver for AMD GPUs, where the debugfs test-IB interface is present. The sources do not describe a trigger that a non-root user can reach, so machines without AMD GPUs or without the amdgpu driver can skip it.
No product ranges from the sources yet.
uname -r and check whether the running kernel includes the upstream commit ec30a576c2d4c0364549e6c04218f50704ef56c8 or a stable backport of itEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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)
This page as .md · .json · in your agent: get_signal("CVE-2026-98519")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.