Answer in brief
CVE-2026-53377 records a Unknown severity vulnerability in drm/msm: always recover the gpu. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c8af219d18502c52319df8d4e3dcfe29a3ca31ab <01930f94b8b13400f3346044cacf98f01d337f3d || >=c8af219d18502c52319df8d4e3dcfe29a3ca31ab <1c0034c1a614a118acbb4bdf7ab51490ee919ad2 || >=c8af219d18502c52319df8d4e3dcfe29a3ca31ab <132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d || >=c8af219d18502c52319df8d4e3dcfe29a3ca31ab <2f5c90478749dfd9a32386100b6078a364298b01 || >=c8af219d18502c52319df8d4e3dcfe29a3ca31ab <01a0d6cd7032e9993feea19fadb03ef9d5b488f2 | 01930f94b8b13400f3346044cacf98f01d337f3d, 1c0034c1a614a118acbb4bdf7ab51490ee919ad2, 132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d, 2f5c90478749dfd9a32386100b6078a364298b01, 01a0d6cd7032e9993feea19fadb03ef9d5b488f2 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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/
Quoted source text, attributed separately from HOL analysis.