[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025120939-CVE-2023-53780-914d@gregkh>
Date: Tue, 9 Dec 2025 09:02:01 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53780: drm/amd/display: fix FCLK pstate change underflow
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: fix FCLK pstate change underflow
[Why]
Currently we set FCLK p-state change
watermark calculated based on dummy
p-state latency when UCLK p-state is
not supported
[How]
Calculate FCLK p-state change watermark
based on on FCLK pstate change latency
in case UCLK p-state is not supported
The Linux kernel CVE team has assigned CVE-2023-53780 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.16 with commit 4bdfa48d74649898468a0bf5c8b8a48dded77b4a
Fixed in 6.2.3 with commit 6853d56dba56d1c24db403ff3885c71e18d572c4
Fixed in 6.3 with commit 972243f973eb0821084e5833d5f7f4ed025f42da
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-53780
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/dml/dcn32/dcn32_fpu.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/4bdfa48d74649898468a0bf5c8b8a48dded77b4a
https://git.kernel.org/stable/c/6853d56dba56d1c24db403ff3885c71e18d572c4
https://git.kernel.org/stable/c/972243f973eb0821084e5833d5f7f4ed025f42da
Powered by blists - more mailing lists