CVE-2026-53020

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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
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:

um: Fix potential race condition in TLB sync

During the TLB sync, we need to traverse and modify the page table, so we should hold the page table lock. Since full SMP support for threads within the same process is still missing, let's disable the split page table lock for simplicity.

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

July 15, 2026

Advisory Details (2)

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

um: Fix potential race condition in TLB sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

um: Fix potential race condition in TLB sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/102331b66bcaf1f41f50b9c4cd5c36e46bafa9f3

Vendor Advisories for CVE-2026-53020(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-07-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-07-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-07-27ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-27ubuntu

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.

Weakness Classification(1)

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

All Vendor Advisories

(5)

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 13× in last 7d / 73× 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-29 12:28 UTCGHSA enrichment
  2. 2026-07-29 00:54 UTCGHSA enrichment
  3. 2026-07-28 05:49 UTCGHSA enrichment
  4. 2026-07-27 17:38 UTCEG score recompute
  5. 2026-07-27 17:38 UTCGHSA enrichment
  6. 2026-07-27 03:09 UTCVendor advisory
  7. 2026-07-27 03:09 UTCGHSA enrichment
  8. 2026-07-26 15:35 UTCEG score recompute
  9. 2026-07-26 15:34 UTCGHSA enrichment
  10. 2026-07-26 14:54 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:19 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 14:31 UTCEPSS rescore
  18. 2026-07-19 02:29 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-16 22:42 UTCGHSA enrichment
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-16 11:09 UTCGHSA enrichment
  23. 2026-07-15 23:33 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 59 more
  1. 2026-07-15 12:00 UTCGHSA enrichment
  2. 2026-07-14 23:41 UTCGHSA enrichment
  3. 2026-07-14 11:49 UTCGHSA enrichment
  4. 2026-07-14 00:14 UTCGHSA enrichment
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 12:40 UTCGHSA enrichment
  7. 2026-07-13 01:07 UTCGHSA enrichment
  8. 2026-07-12 13:34 UTCGHSA enrichment
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-12 01:57 UTCGHSA enrichment
  11. 2026-07-11 14:24 UTCGHSA enrichment
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 02:23 UTCGHSA enrichment
  15. 2026-07-10 14:47 UTCGHSA enrichment
  16. 2026-07-10 03:14 UTCGHSA enrichment
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 15:40 UTCGHSA enrichment
  20. 2026-07-09 04:07 UTCGHSA enrichment
  21. 2026-07-08 16:30 UTCGHSA enrichment
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 04:57 UTCGHSA enrichment
  25. 2026-07-07 16:54 UTCGHSA enrichment
  26. 2026-07-07 13:46 UTCEPSS rescore
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 04:00 UTCGHSA enrichment
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 16:27 UTCEPSS rescore
  31. 2026-07-06 16:07 UTCGHSA enrichment
  32. 2026-07-06 04:30 UTCGHSA enrichment
  33. 2026-07-05 16:53 UTCGHSA enrichment
  34. 2026-07-05 05:16 UTCGHSA enrichment
  35. 2026-07-05 02:31 UTCEPSS rescore
  36. 2026-07-05 02:30 UTCEPSS rescore
  37. 2026-07-04 17:30 UTCGHSA enrichment
  38. 2026-07-04 06:31 UTCEPSS rescore
  39. 2026-07-04 05:57 UTCGHSA enrichment
  40. 2026-07-03 18:18 UTCGHSA enrichment
  41. 2026-07-03 06:44 UTCGHSA enrichment
  42. 2026-07-02 19:10 UTCGHSA enrichment
  43. 2026-07-02 07:37 UTCGHSA enrichment
  44. 2026-07-01 20:04 UTCGHSA enrichment
  45. 2026-07-01 15:07 UTCEPSS rescore
  46. 2026-07-01 08:31 UTCEG score recompute▲ 7.80
  47. 2026-07-01 08:31 UTCGHSA enrichment
  48. 2026-06-30 23:22 UTCEPSS rescore
  49. 2026-06-29 14:06 UTCEPSS rescore
  50. 2026-06-29 14:06 UTCEPSS rescore
  51. 2026-06-28 14:07 UTCEPSS rescore
  52. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  53. 2026-06-28 04:56 UTCEPSS rescore
  54. 2026-06-28 04:56 UTCEPSS rescore
  55. 2026-06-28 01:26 UTCGHSA enrichment
  56. 2026-06-27 03:08 UTCEPSS rescore
  57. 2026-06-25 13:49 UTCEPSS rescore
  58. 2026-06-24 18:21 UTCEG score recompute
  59. 2026-06-24 18:02 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53020?
CVE-2026-53020 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: um: Fix potential race condition in TLB sync During the TLB sync, we need to traverse and modify the page table, so we should hold the page table lock. Since full SMP support for threads within the same process is still missing,…
When was CVE-2026-53020 disclosed?
CVE-2026-53020 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53020 actively exploited?
CVE-2026-53020 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53020?
CVE-2026-53020 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53020, 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-53020

Explore →

Is Your Infrastructure Affected by CVE-2026-53020?

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

Start Free Scan →Browse All CVEs