---
id: CVE-2026-53377
title: |-
  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
  s…
summary: |-
  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
  s…
severity: none
published: '2026-07-19'
updated: '2026-07-19'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-53377'
references:
  - url: 'https://git.kernel.org/stable/c/01a0d6cd7032e9993feea19fadb03ef9d5b488f2'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2f5c90478749dfd9a32386100b6078a364298b01'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/01930f94b8b13400f3346044cacf98f01d337f3d'
  - url: 'https://git.kernel.org/stable/c/1c0034c1a614a118acbb4bdf7ab51490ee919ad2'
tags:
  - nvd
  - cve.org
ingestedAt: '2026-07-19T16:31:24.264Z'
epss: 0.00125
epssPercentile: 0.02171
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= c8af219d18502c52319df8d4e3dcfe29a3ca31ab <
    01930f94b8b13400f3346044cacf98f01d337f3d
  - >-
    Linux >= c8af219d18502c52319df8d4e3dcfe29a3ca31ab <
    1c0034c1a614a118acbb4bdf7ab51490ee919ad2
  - >-
    Linux >= c8af219d18502c52319df8d4e3dcfe29a3ca31ab <
    132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d
  - >-
    Linux >= c8af219d18502c52319df8d4e3dcfe29a3ca31ab <
    2f5c90478749dfd9a32386100b6078a364298b01
  - >-
    Linux >= c8af219d18502c52319df8d4e3dcfe29a3ca31ab <
    01a0d6cd7032e9993feea19fadb03ef9d5b488f2
  - Linux 5.19
---

## Overview

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/

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.