drm/amd/display: Increase block_sequence array size
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's AMD display driver can generate more steps than its block_sequence buffer holds. On a six-pipe ASIC with all pipes in one MPC chain, this can corrupt adjacent data and cause a crash. The input does not establish how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running Linux kernels with AMD display support should check their exposure; affected versions are not specified.