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
3%
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(8)

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

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 (137 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

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 31× in last 7d / 149× 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 233 total refreshes for this CVE.

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