Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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/

Timeline

  1. ID reserved

    By Linux

  2. · 40 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53377, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected c8af219d18502c52319df8d4e3dcfe29a3ca31ab – < f8410426e46a8449a3734b037286cbafe0110033
    • affected c8af219d18502c52319df8d4e3dcfe29a3ca31ab – < 01930f94b8b13400f3346044cacf98f01d337f3d
    • affected c8af219d18502c52319df8d4e3dcfe29a3ca31ab – < 1c0034c1a614a118acbb4bdf7ab51490ee919ad2
    • affected c8af219d18502c52319df8d4e3dcfe29a3ca31ab – < 132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d
    • affected c8af219d18502c52319df8d4e3dcfe29a3ca31ab – < 2f5c90478749dfd9a32386100b6078a364298b01
    • affected c8af219d18502c52319df8d4e3dcfe29a3ca31ab – < 01a0d6cd7032e9993feea19fadb03ef9d5b488f2
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.32 – ≤ 6.18.*
    • unaffected 7.0.9 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53377 badge
[![CVE-2026-53377](https://cveledger.app/badge/CVE-2026-53377.svg)](https://cveledger.app/cve/CVE-2026-53377)

Record last updated .