drm/amd/display: fix dc_lock leak on GPU reset error paths
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.51, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In 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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3cf7a0bc87f028b6bc63a43a80d9d6026ae4d85f · fixed in 295d2bf42061db490254e748f9344545bb7faf19; From 3cf7a0bc87f028b6bc63a43a80d9d6026ae4d85f · fixed in dac29cbb405b912742f4f7eda833cec8e7a53780; From 3cf7a0bc87f028b6bc63a43a80d9d6026ae4d85f · fixed in 92a9eebd2a1f892fe482154d83f9f1626bc73d3b
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5