drm/amd/display: Wake DMCUB before executing GPINT commands
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2ef98c6d753a744e333b7e34b9cf687040fba57d and Kernel e5ffd1263dd5b44929c676171802e7b6af483f21.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.15, >=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <2ef98c6d753a744e333b7e34b9cf687040fba57d, >=4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c <e5ffd1263dd5b44929c676171802e7b6af483f21 | 2ef98c6d753a744e333b7e34b9cf687040fba57d, e5ffd1263dd5b44929c676171802e7b6af483f21 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket