linux-cve-announce - CVE-2025-38030: Revert "drm/amd: Keep display off while going into S4"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025061824-CVE-2025-38030-9e7b@gregkh>
Date: Wed, 18 Jun 2025 11:33:26 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38030: Revert "drm/amd: Keep display off while going into S4"

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

Revert "drm/amd: Keep display off while going into S4"

commit 68bfdc8dc0a1a ("drm/amd: Keep display off while going into S4")
attempted to keep displays off during the S4 sequence by not resuming
display IP.  This however leads to hangs because DRM clients such as the
console can try to access registers and cause a hang.

(cherry picked from commit e485502c37b097b0bd773baa7e2741bf7bd2909a)

The Linux kernel CVE team has assigned CVE-2025-38030 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.15 with commit 68bfdc8dc0a1a7fdd9ab61e69907ae71a6fd3d91 and fixed in 5.15.185 with commit ff887e77b777e806b5210eba229e0bd657e07b60
	Issue introduced in 6.15 with commit 68bfdc8dc0a1a7fdd9ab61e69907ae71a6fd3d91 and fixed in 6.1.141 with commit 9c40d1f7b75fc93d7ef02acc3a2a712cb057e576
	Issue introduced in 6.15 with commit 68bfdc8dc0a1a7fdd9ab61e69907ae71a6fd3d91 and fixed in 6.6.93 with commit ed7d24b0c375f74a1956e73d53549be78bf2774c
	Issue introduced in 6.15 with commit 68bfdc8dc0a1a7fdd9ab61e69907ae71a6fd3d91 and fixed in 6.12.31 with commit 7c220f89add8e7d6db63c9c4d9566917f8175a0b
	Issue introduced in 6.15 with commit 68bfdc8dc0a1a7fdd9ab61e69907ae71a6fd3d91 and fixed in 6.14.9 with commit edfb7f9d27e2cd9aad55cfb5aaa6c67801613e6a

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-2025-38030
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/display/amdgpu_dm/amdgpu_dm.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/ff887e77b777e806b5210eba229e0bd657e07b60
	https://git.kernel.org/stable/c/9c40d1f7b75fc93d7ef02acc3a2a712cb057e576
	https://git.kernel.org/stable/c/ed7d24b0c375f74a1956e73d53549be78bf2774c
	https://git.kernel.org/stable/c/7c220f89add8e7d6db63c9c4d9566917f8175a0b
	https://git.kernel.org/stable/c/edfb7f9d27e2cd9aad55cfb5aaa6c67801613e6a
	https://git.kernel.org/stable/c/7e7cb7a13c81073d38a10fa7b450d23712281ec4