CVE-2026-53054

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

drm/msm: Fix VM_BIND UNMAP locking

Wrong argument meant that the objs involved in UNMAP ops were not always getting locked.

Since _NO_SHARE objs share a common resv with the VM (which is always locked) this would only show up with non-_NO_SHARE BOs.

Patchwork: https://patchwork.freedesktop.org/patch/713898/

CVSS v3
7.8
EG Score
7.8(high)
EPSS
2.7%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

drm/msm: Fix VM_BIND UNMAP locking - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9ecf758270501b2e7a0bc1dd69a6f28f1ae3cae
generic

drm/msm: Fix VM_BIND UNMAP locking - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/85042c2cd970a6b0e686329387096fe19989ae62
generic

drm/msm: Fix VM_BIND UNMAP locking - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/206f812ef140727b75697111391ae320fd8aa652

Vendor Advisories for CVE-2026-53054(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 45× 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.

  1. 2026-07-07 02:19 UTCEG score recompute
  2. 2026-07-07 02:19 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 15:29 UTCEG score recompute
  6. 2026-07-06 15:28 UTCGHSA enrichment
  7. 2026-07-06 04:30 UTCEG score recompute
  8. 2026-07-06 04:30 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 17:36 UTCEG score recompute
  12. 2026-07-05 17:36 UTCGHSA enrichment
  13. 2026-07-05 06:46 UTCEG score recompute
  14. 2026-07-05 06:46 UTCGHSA enrichment
  15. 2026-07-04 19:55 UTCEG score recompute
  16. 2026-07-04 19:55 UTCGHSA enrichment
  17. 2026-07-04 09:05 UTCEG score recompute
  18. 2026-07-04 09:05 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-03 22:15 UTCEG score recompute
  21. 2026-07-03 22:15 UTCGHSA enrichment
  22. 2026-07-03 11:25 UTCEG score recompute
  23. 2026-07-03 11:25 UTCGHSA enrichment
  24. 2026-07-03 00:30 UTCEG score recompute
  25. 2026-07-03 00:29 UTCGHSA enrichment
Show 20 more
  1. 2026-07-02 13:39 UTCEG score recompute
  2. 2026-07-02 13:39 UTCGHSA enrichment
  3. 2026-07-02 02:49 UTCEG score recompute
  4. 2026-07-02 02:49 UTCGHSA enrichment
  5. 2026-07-01 15:58 UTCEG score recompute
  6. 2026-07-01 15:58 UTCGHSA enrichment
  7. 2026-07-01 05:07 UTCEG score recompute▲ 7.80
  8. 2026-07-01 05:07 UTCGHSA enrichment
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 23:43 UTCEG score recompute
  16. 2026-06-27 23:42 UTCGHSA enrichment
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 18:17 UTCEG score recompute
  20. 2026-06-24 18:03 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53054?
CVE-2026-53054 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix VM_BIND UNMAP locking Wrong argument meant that the objs involved in UNMAP ops were not always getting locked. Since NOSHARE objs share a common resv with the VM (which is always locked) this would only show up with…
When was CVE-2026-53054 disclosed?
CVE-2026-53054 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53054 actively exploited?
CVE-2026-53054 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53054?
CVE-2026-53054 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53054?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53054, 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

Explore the affected products and dependency analysis for CVE-2026-53054

Explore →

Is Your Infrastructure Affected by CVE-2026-53054?

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

Start Free Scan →Browse All CVEs