drm/amd/display: Wake DMCUB before executing GPINT commands
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: Wake DMCUB before executing GPINT commands
[Why] DMCUB can be in idle when we attempt to interface with the HW through the GPINT mailbox resulting in a system hang.
[How] Add dc_wake_and_execute_gpint() to wrap the wake, execute, sleep sequence.
If the GPINT executes successfully then DMCUB will be put back into sleep after the optional response is returned.
It functions similar to the inbox command interface.
From the CVE record · Linux
The Linux kernel's AMD display driver can hang the system if it sends a GPINT command while DMCUB is idle. The input does not establish whether an attacker can trigger this condition or specify access or user-interaction requirements.
Engineers running the Linux kernel with AMD display support should check their installations; affected versions are not specified.