drm/msm: always recover the gpu
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c8af219d18502c52319df8d4e3dcfe29a3ca31ab · < 01a0d6cd7032e9993feea19fadb03ef9d5b488f2| No fix yet |
| Linux Linux |
|
|
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/
From the CVE record · Linux
The drm/msm recovery worker can skip GPU recovery when a ring has no more work, leaving the GPU hung. More work submitted before the GPU suspends and resumes may trigger another timeout. The input does not specify attacker access, authentication requirements, or user interaction.
Engineers running the Linux kernel with drm/msm should check their kernel; affected versions are not specified.