VulnerabilityPublished 19 Jul 2026Updated 21 Oct 2026

CVE-2026-53377: Linux kernel · drm/msm: always recover the gpu

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in 01930f94b8b13400f3346044cacf98f01d337f3d : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 01930f94b8b13400f3346044cacf98f01d337f3d, 132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d, 2f5c90478749dfd9a32386100b6078a364298b01 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ c8af219d18502c52319df8d4e3dcfe29a3ca31ab, < 01930f94b8b13400f3346044cacf98f01d337f3d	Fixed in 01930f94b8b13400f3346044cacf98f01d337f3d
LinuxLinux	Affected ≥ c8af219d18502c52319df8d4e3dcfe29a3ca31ab, < 132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d	Fixed in 132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d
LinuxLinux	Affected ≥ c8af219d18502c52319df8d4e3dcfe29a3ca31ab, < 2f5c90478749dfd9a32386100b6078a364298b01	Fixed in 2f5c90478749dfd9a32386100b6078a364298b01
LinuxLinux	Affected ≥ c8af219d18502c52319df8d4e3dcfe29a3ca31ab, < 1c0034c1a614a118acbb4bdf7ab51490ee919ad2	Fixed in 1c0034c1a614a118acbb4bdf7ab51490ee919ad2
LinuxLinux	Affected ≥ c8af219d18502c52319df8d4e3dcfe29a3ca31ab, < 01a0d6cd7032e9993feea19fadb03ef9d5b488f2	Fixed in 01a0d6cd7032e9993feea19fadb03ef9d5b488f2
LinuxLinux	Affected =5.19	Fixed in–

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/

References

Community reviews

Loading reviews…