CVE-2026-53054

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 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.

Patch Availability(9)

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

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(9)

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 12× in last 7d / 57× 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 265 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53054?
CVE-2026-53054 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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