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… (CVE-2026-53377)
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/
AI Analysis
Technical Summary
The Linux kernel drm/msm GPU driver previously did not always trigger GPU recovery when the GPU hung if there was no more work queued. The recover_worker function would early exit if only one job caused a hang, relying on the GPU suspending and resuming to clear the hang state. Since there was no guarantee the GPU would suspend and resume before new work arrived, the GPU could remain hung and cause repeated timeouts. The fix ensures the GPU is always recovered immediately when a hang is detected, preventing persistent hung states.
Potential Impact
This vulnerability can cause the GPU to remain in a hung state, resulting in denial of service conditions where GPU operations are stalled or time out. There is no impact on confidentiality or integrity reported. The primary impact is availability degradation due to GPU hangs.
Mitigation Recommendations
A patch has been applied to the Linux kernel drm/msm driver to always recover the GPU when a hang is detected. Users should update to a kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or kernel mailing list advisories for the exact fixed versions and apply updates accordingly.
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… (CVE-2026-53377)
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/
CVSS v3.1
Score 5.5medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel drm/msm GPU driver previously did not always trigger GPU recovery when the GPU hung if there was no more work queued. The recover_worker function would early exit if only one job caused a hang, relying on the GPU suspending and resuming to clear the hang state. Since there was no guarantee the GPU would suspend and resume before new work arrived, the GPU could remain hung and cause repeated timeouts. The fix ensures the GPU is always recovered immediately when a hang is detected, preventing persistent hung states.
Potential Impact
This vulnerability can cause the GPU to remain in a hung state, resulting in denial of service conditions where GPU operations are stalled or time out. There is no impact on confidentiality or integrity reported. The primary impact is availability degradation due to GPU hangs.
Mitigation Recommendations
A patch has been applied to the Linux kernel drm/msm driver to always recover the GPU when a hang is detected. Users should update to a kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or kernel mailing list advisories for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9q28-3qg6-wq2f
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53377"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27ad2a4a8d598913229d
Added to database: 07/19/2026, 19:38:21 UTC
Last enriched: 07/30/2026, 12:03:13 UTC
Last updated: 08/31/2026, 10:52:10 UTC
Views: 71
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.