drm/amd/display: Disable idle reallow as part of command/gpint execution
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: Disable idle reallow as part of command/gpint execution
[Why] Workaroud for a race condition where DMCUB is in the process of committing to IPS1 during the handshake causing us to miss the transition into IPS2 and touch the INBOX1 RPTR causing a HW hang.
[How] Disable the reallow to ensure that we have enough of a gap between entry and exit and we're not seeing back-to-back wake_and_executes.
From the CVE record · Linux
A race condition in the Linux kernel’s AMD display driver can cause a hardware hang during command or GPINT execution if DMCUB is committing to IPS1 during a handshake. The input does not specify an attacker action, access requirement, or user interaction needed to trigger it.
Engineers running Linux kernels with the AMD display driver should check their versions against the vendor advisory; affected versions are not specified.