drm/amd/display: fix dc_lock leak on GPU reset error paths
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 |
|
|
6.18.517.2.57.3In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: fix dc_lock leak on GPU reset error paths
On GPU reset, dm_suspend() takes dc_lock and leaves it for dm_resume() to drop. If amdgpu_dm_commit_zero_streams() or dm_dmub_hw_init() fails, the function returns with the lock still held. The matching resume path is then skipped, so every later dc_lock take hangs.
Release the cached DC state and unlock before returning the error.
From the CVE record · Linux
In the Linux kernel’s AMD display driver, a GPU reset can leave dc_lock held if amdgpu_dm_commit_zero_streams() or dm_dmub_hw_init() fails. Later attempts to take the lock then hang; the input does not establish whether an attacker can trigger this or what access they would need.
Engineers running the Linux kernel with AMD display support should check their installations; affected versions were not provided.