drm/msm: always recover the gpu
- 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.6.160, 6.12.114, 6.18.32, 7.0.9
- 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/msm: always recover the gpu Previously, in case there was no more work to do, recover worker wouldn't trigger recovery and would instead rely on the gpu going to sleep and then resuming when more work is submitted. Recover_worker will first increment the fence of the hung ring so, if there's only one job submitted to a ring and that causes an hang, it will early out. There's no guarantee that the gpu will suspend and resume before more work is submitted and if the gpu is in a hung state it will stay in that state and probably trigger a timeout again. Just stop checking and always recover the gpu. Patchwork: https://patchwork.freedesktop.org/patch/704066/
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From c8af219d18502c52319df8d4e3dcfe29a3ca31ab · fixed in 01930f94b8b13400f3346044cacf98f01d337f3d; From c8af219d18502c52319df8d4e3dcfe29a3ca31ab · fixed in 1c0034c1a614a118acbb4bdf7ab51490ee919ad2; From c8af219d18502c52319df8d4e3dcfe29a3ca31ab · fixed in 132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d; From c8af219d18502c52319df8d4e3dcfe29a3ca31ab · fixed in 2f5c90478749dfd9a32386100b6078a364298b01; From c8af219d18502c52319df8d4e3dcfe29a3ca31ab · fixed in 01a0d6cd7032e9993feea19fadb03ef9d5b488f2
- Linux Linux
5.19
- KernelLinux
From 5.19.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.32; From 6.19.0 · fixed in 7.0.9