[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091503-CVE-2023-53258-35f0@gregkh>
Date: Mon, 15 Sep 2025 16:46:33 +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-53258: drm/amd/display: Fix possible underflow for displays with large vblank
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix possible underflow for displays with large vblank
[Why]
Underflow observed when using a display with a large vblank region
and low refresh rate
[How]
Simplify calculation of vblank_nom
Increase value for VBlankNomDefaultUS to 800us
The Linux kernel CVE team has assigned CVE-2023-53258 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.43 with commit d5741133e6e2f304b40ca1da0e16f62af06f4d22
Fixed in 6.4.8 with commit 64bc8e10c87adf60b2d32aacf3afb288e51d5a62
Fixed in 6.5 with commit 1a4bcdbea4319efeb26cc4b05be859a7867e02dc
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-53258
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/dcn314/dcn314_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/d5741133e6e2f304b40ca1da0e16f62af06f4d22
https://git.kernel.org/stable/c/64bc8e10c87adf60b2d32aacf3afb288e51d5a62
https://git.kernel.org/stable/c/1a4bcdbea4319efeb26cc4b05be859a7867e02dc
Powered by blists - more mailing lists