linux-cve-announce - CVE-2023-53042: drm/amd/display: Do not set DRR on pipe Commit

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: <2025050203-CVE-2023-53042-e4e8@gregkh>
Date: Fri,  2 May 2025 17:55:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53042: drm/amd/display: Do not set DRR on pipe Commit

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

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

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

drm/amd/display: Do not set DRR on pipe Commit

[WHY]
Writing to DRR registers such as OTG_V_TOTAL_MIN on the same frame as a
pipe commit can cause underflow.

The Linux kernel CVE team has assigned CVE-2023-53042 to this issue.


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

	Fixed in 6.1.21 with commit f8080f1e300e7abcc03025ec8b5bab69ae98daaa
	Fixed in 6.2.8 with commit 3c20a098b507020936e02a98f4fbb924deeef44b
	Fixed in 6.3 with commit 56574f89dbd84004c3fd6485bcaafb5aa9b8be14

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-2023-53042
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/dc/dcn30/dcn30_hwseq.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/f8080f1e300e7abcc03025ec8b5bab69ae98daaa
	https://git.kernel.org/stable/c/3c20a098b507020936e02a98f4fbb924deeef44b
	https://git.kernel.org/stable/c/56574f89dbd84004c3fd6485bcaafb5aa9b8be14