From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98519: drm/amdgpu: Fix runtime PM leak in amdgpu_debugfs_test_ib_show()
Date: Sun, 18 Oct 2026 17:16:23 +0200 [thread overview]
Message-ID: <2026101822-CVE-2026-98519-124c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
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)
The Linux kernel CVE team has assigned CVE-2026-98519 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit 6049db43d6dd9cbb9d7f897839d15b0bc600e23c and fixed in 6.1.189 with commit fc5606ac91642d0f184b83ab833148c457c3c331
Issue introduced in 5.10 with commit 6049db43d6dd9cbb9d7f897839d15b0bc600e23c and fixed in 6.6.158 with commit 2c1a643942caae938ea84df2648a9b0c136e09be
Issue introduced in 5.10 with commit 6049db43d6dd9cbb9d7f897839d15b0bc600e23c and fixed in 6.12.112 with commit e016347fb1829489e062ea51a98a51f48b1d582d
Issue introduced in 5.10 with commit 6049db43d6dd9cbb9d7f897839d15b0bc600e23c and fixed in 6.18.55 with commit c28e74395ab09922bbf5be42bc5a6ed1ba4f3c37
Issue introduced in 5.10 with commit 6049db43d6dd9cbb9d7f897839d15b0bc600e23c and fixed in 7.2.9 with commit 2556dd3a36beb3a11041ef01b5e9762e2157909f
Issue introduced in 5.10 with commit 6049db43d6dd9cbb9d7f897839d15b0bc600e23c and fixed in 7.3-rc5 with commit 2b86ab1bd6673c525adda88819d7658ba9e784ec
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-98519
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/fc5606ac91642d0f184b83ab833148c457c3c331
https://git.kernel.org/stable/c/2c1a643942caae938ea84df2648a9b0c136e09be
https://git.kernel.org/stable/c/e016347fb1829489e062ea51a98a51f48b1d582d
https://git.kernel.org/stable/c/c28e74395ab09922bbf5be42bc5a6ed1ba4f3c37
https://git.kernel.org/stable/c/2556dd3a36beb3a11041ef01b5e9762e2157909f
https://git.kernel.org/stable/c/2b86ab1bd6673c525adda88819d7658ba9e784ec
reply other threads:[~2026-10-18 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026101822-CVE-2026-98519-124c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.