[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050959-CVE-2025-37870-311a@gregkh>
Date: Fri, 9 May 2025 08:44:04 +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-37870: drm/amd/display: prevent hang on link training fail
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: prevent hang on link training fail
[Why]
When link training fails, the phy clock will be disabled. However, in
enable_streams, it is assumed that link training succeeded and the
mux selects the phy clock, causing a hang when a register write is made.
[How]
When enable_stream is hit, check if link training failed. If it did, fall
back to the ref clock to avoid a hang and keep the system in a recoverable
state.
The Linux kernel CVE team has assigned CVE-2025-37870 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.25 with commit 0363c03672cd3191f037905bf981eb523a3b71b1
Fixed in 6.14.4 with commit 04bf4f2a497e9877c425c5124652e61fb8a1a0aa
Fixed in 6.15-rc1 with commit 8058061ed9d6bc259d1e678607b07d259342c08f
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-37870
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/hwss/dcn20/dcn20_hwseq.c
drivers/gpu/drm/amd/display/dc/hwss/dcn401/dcn401_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/0363c03672cd3191f037905bf981eb523a3b71b1
https://git.kernel.org/stable/c/04bf4f2a497e9877c425c5124652e61fb8a1a0aa
https://git.kernel.org/stable/c/8058061ed9d6bc259d1e678607b07d259342c08f
Powered by blists - more mailing lists