Description
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/
Affected products
linux: linux kernel
References6
- git.kernel.org/stable/c/01a0d6cd7032e9993feea19fadb03ef9d5b488f2 Patch
- git.kernel.org/stable/c/132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d Patch
- git.kernel.org/stable/c/2f5c90478749dfd9a32386100b6078a364298b01 Patch
- git.kernel.org/stable/c/01930f94b8b13400f3346044cacf98f01d337f3d
- git.kernel.org/stable/c/1c0034c1a614a118acbb4bdf7ab51490ee919ad2
- git.kernel.org/stable/c/f8410426e46a8449a3734b037286cbafe0110033
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 2 · as of 14 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.