CVE-2026-53377

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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/

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 29, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
No patch confirmed yet.
generic

drm/msm: always recover the gpu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2f5c90478749dfd9a32386100b6078a364298b01
generic

drm/msm: always recover the gpu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/132b8d51f0ffbee6e4e1ebbe1a50330aaf2dbd5d
generic

drm/msm: always recover the gpu - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01a0d6cd7032e9993feea19fadb03ef9d5b488f2

Vendor Advisories for CVE-2026-53377(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-07ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-07ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-07ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-07ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-07ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-07ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.9-1—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 149 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 23:48 UTCEG score recompute
  5. 2026-09-07 23:48 UTCVendor advisory
  6. 2026-09-07 23:48 UTCGHSA enrichment
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 20:22 UTCEG score recompute
  10. 2026-09-05 20:22 UTCVendor advisory
  11. 2026-09-05 20:21 UTCGHSA enrichment
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:12 UTCEPSS rescore
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-31 03:49 UTCEG score recompute
  17. 2026-08-31 03:49 UTCVendor advisory
  18. 2026-08-31 03:49 UTCGHSA enrichment
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 03:05 UTCEG score recompute
  21. 2026-08-30 03:05 UTCVendor advisory
  22. 2026-08-30 03:05 UTCGHSA enrichment
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 15:16 UTCEG score recompute
Show 75 more
  1. 2026-08-27 15:16 UTCVendor advisory
  2. 2026-08-27 15:16 UTCGHSA enrichment
  3. 2026-08-27 14:25 UTCEPSS rescore
  4. 2026-08-26 13:43 UTCEG score recompute
  5. 2026-08-26 13:43 UTCVendor advisory
  6. 2026-08-26 13:43 UTCGHSA enrichment
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-25 13:00 UTCEG score recompute
  9. 2026-08-25 13:00 UTCVendor advisory
  10. 2026-08-25 13:00 UTCGHSA enrichment
  11. 2026-08-24 12:16 UTCEG score recompute
  12. 2026-08-24 12:16 UTCVendor advisory
  13. 2026-08-24 12:16 UTCGHSA enrichment
  14. 2026-08-23 11:05 UTCEG score recompute
  15. 2026-08-23 11:05 UTCVendor advisory
  16. 2026-08-23 11:05 UTCGHSA enrichment
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 10:21 UTCEG score recompute
  19. 2026-08-22 10:21 UTCVendor advisory
  20. 2026-08-22 10:21 UTCGHSA enrichment
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 09:30 UTCEG score recompute
  23. 2026-08-21 09:30 UTCVendor advisory
  24. 2026-08-21 09:30 UTCGHSA enrichment
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-20 08:47 UTCEG score recompute
  27. 2026-08-20 08:47 UTCVendor advisory
  28. 2026-08-20 08:47 UTCGHSA enrichment
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-19 08:04 UTCEG score recompute
  31. 2026-08-19 08:04 UTCVendor advisory
  32. 2026-08-19 08:04 UTCGHSA enrichment
  33. 2026-08-18 07:19 UTCEG score recompute
  34. 2026-08-18 07:19 UTCVendor advisory
  35. 2026-08-18 07:19 UTCGHSA enrichment
  36. 2026-08-17 13:47 UTCEPSS rescore
  37. 2026-08-17 06:35 UTCEG score recompute
  38. 2026-08-17 06:35 UTCVendor advisory
  39. 2026-08-17 06:35 UTCGHSA enrichment
  40. 2026-08-16 14:56 UTCEPSS rescore
  41. 2026-08-16 05:36 UTCEG score recompute
  42. 2026-08-16 05:36 UTCVendor advisory
  43. 2026-08-16 05:36 UTCGHSA enrichment
  44. 2026-08-16 02:14 UTCEPSS rescore
  45. 2026-08-15 04:53 UTCEG score recompute
  46. 2026-08-15 04:53 UTCVendor advisory
  47. 2026-08-15 04:53 UTCGHSA enrichment
  48. 2026-08-15 01:30 UTCEPSS rescore
  49. 2026-08-14 04:09 UTCEG score recompute
  50. 2026-08-14 04:09 UTCVendor advisory
  51. 2026-08-14 04:09 UTCGHSA enrichment
  52. 2026-08-13 22:00 UTCEPSS rescore
  53. 2026-08-13 03:25 UTCEG score recompute
  54. 2026-08-13 03:25 UTCVendor advisory
  55. 2026-08-13 03:25 UTCGHSA enrichment
  56. 2026-08-12 13:51 UTCEPSS rescore
  57. 2026-08-12 02:42 UTCEG score recompute
  58. 2026-08-12 02:42 UTCVendor advisory
  59. 2026-08-12 02:42 UTCGHSA enrichment
  60. 2026-08-11 01:58 UTCEG score recompute
  61. 2026-08-11 01:58 UTCVendor advisory
  62. 2026-08-11 01:58 UTCGHSA enrichment
  63. 2026-08-11 00:00 UTCEPSS rescore
  64. 2026-08-10 01:15 UTCEG score recompute
  65. 2026-08-10 01:15 UTCVendor advisory
  66. 2026-08-10 01:15 UTCGHSA enrichment
  67. 2026-08-09 13:46 UTCEPSS rescore
  68. 2026-08-09 00:32 UTCEG score recompute
  69. 2026-08-09 00:32 UTCVendor advisory
  70. 2026-08-09 00:32 UTCGHSA enrichment
  71. 2026-08-08 16:37 UTCEPSS rescore
  72. 2026-08-07 23:48 UTCVendor advisory
  73. 2026-08-07 23:48 UTCGHSA enrichment
  74. 2026-08-06 23:05 UTCEG score recompute
  75. 2026-08-06 23:05 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-53377?
CVE-2026-53377 is a medium vulnerability published on July 19, 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.…
When was CVE-2026-53377 disclosed?
CVE-2026-53377 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53377 actively exploited?
CVE-2026-53377 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53377?
CVE-2026-53377 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53377?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53377, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53377

Explore →

Is Your Infrastructure Affected by CVE-2026-53377?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs