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/
Published: 2026-07-19
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw, a CWE-772 weakness involving improper resource recovery, occurs in the drm/msm driver when the recover_worker does not trigger a GPU recovery after a hang. Because the worker only increments the ring fence and exits, the GPU remains in a failed state, preventing subsequent work and potentially exhausting resources.

Affected Systems

The vulnerability affects the Linux kernel as a whole, with all distributions that ship an unpatched drm/msm driver. No specific version range is listed, but any kernel that includes the buggy recover_worker logic is susceptible until the fix is applied.

Risk and Exploitability

The exploit probability is very low (EPSS < 1%) and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a privileged local user submitting workloads that cause a GPU hang on systems using GPU acceleration without proper recovery, a scenario inferred from the described flaw. Mitigation hinges on applying the available patch.

Generated by OpenCVE AI on July 30, 2026 at 22:34 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the latest Linux kernel update that includes the drm/msm GPU recovery fix.
  • If a kernel update cannot be applied immediately, restrict GPU usage to trusted contexts or disable GPU processing for unprivileged users.
  • Set up automated monitoring of GPU status and trigger a DRM subsystem reload or system reboot when a GPU hang is detected.

Generated by OpenCVE AI on July 30, 2026 at 22:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
History

Tue, 21 Jul 2026 00:15:00 +0000


Sun, 19 Jul 2026 10:30:00 +0000

Type Values Removed Values Added
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/
Title drm/msm: always recover the gpu
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-07-20T06:41:20.243Z

Reserved: 2026-06-09T07:44:35.401Z

Link: CVE-2026-53377

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity :

Publid Date: 2026-07-19T00:00:00Z

Links: CVE-2026-53377 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T22:45:04Z

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime