CVE-2026-53377: drm/msm: always recover the gpu
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.
Recoverworker 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernel (drm/msm)to a version that resolves this vulnerability.Patch 704066
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53377?
CVE-2026-53377 has a risk rating of 37, indicating a significant vulnerability in the Linux kernel.
How do I fix CVE-2026-53377?
To fix CVE-2026-53377, update your Linux kernel to the latest version where the vulnerability has been addressed.
What systems are affected by CVE-2026-53377?
CVE-2026-53377 affects various versions of the Linux kernel that utilize DRM MSM for GPU management.
What impact does CVE-2026-53377 have on system performance?
CVE-2026-53377 may lead to reduced GPU performance as it improperly handles recovery, potentially affecting application responsiveness.
When was CVE-2026-53377 published?
CVE-2026-53377 was published on July 19, 2026.