drm/amd/display: Refactor DMCUB enter/exit idle interface
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: Refactor DMCUB enter/exit idle interface
[Why] We can hang in place trying to send commands when the DMCUB isn't powered on.
[How] We need to exit out of the idle state prior to sending a command, but the process that performs the exit also invokes a command itself.
Fixing this issue involves the following:
1. Using a software state to track whether or not we need to start the process to exit idle or notify idle.
It's possible for the hardware to have exited an idle state without driver knowledge, but entering one is always restricted to a driver allow - which makes the SW state vs HW state mismatch issue purely one of optimization, which should seldomly be hit, if at all.
2. Refactor any instances of exit/notify idle to use a single wrapper that maintains this SW state.
From the CVE record · Linux
The Linux kernel's AMD display driver can hang while trying to send commands when the DMCUB is not powered on. The input does not describe how an attacker could trigger this condition or specify access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the AMD display driver should check their deployments; affected versions are not specified.