[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061842-CVE-2025-38080-849c@gregkh>
Date: Wed, 18 Jun 2025 11:34:15 +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-38080: drm/amd/display: Increase block_sequence array size
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Increase block_sequence array size
[Why]
It's possible to generate more than 50 steps in hwss_build_fast_sequence,
for example with a 6-pipe asic where all pipes are in one MPC chain. This
overflows the block_sequence buffer and corrupts block_sequence_steps,
causing a crash.
[How]
Expand block_sequence to 100 items. A naive upper bound on the possible
number of steps for a 6-pipe asic, ignoring the potential for steps to be
mutually exclusive, is 91 with current code, therefore 100 is sufficient.
The Linux kernel CVE team has assigned CVE-2025-38080 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.93 with commit de67e80ab48f1f23663831007a2fa3c1471a7757
Fixed in 6.12.31 with commit e55c5704b12eeea27e212bfab8f7e51ad3e8ac1f
Fixed in 6.14.9 with commit bf1666072e7482317cf2302621766482a21a62c7
Fixed in 6.15 with commit 3a7810c212bcf2f722671dadf4b23ff70a7d23ee
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-38080
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/inc/core_types.h
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/de67e80ab48f1f23663831007a2fa3c1471a7757
https://git.kernel.org/stable/c/e55c5704b12eeea27e212bfab8f7e51ad3e8ac1f
https://git.kernel.org/stable/c/bf1666072e7482317cf2302621766482a21a62c7
https://git.kernel.org/stable/c/3a7810c212bcf2f722671dadf4b23ff70a7d23ee
Powered by blists - more mailing lists