CVE-2026-53020

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
Trending — 3 sources updated this week
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:

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(high)
EPSS
2.2%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 28, 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.

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 04:00 UTCEG score recompute
  2. 2026-07-07 04:00 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:07 UTCEG score recompute
  6. 2026-07-06 16:07 UTCGHSA enrichment
  7. 2026-07-06 04:31 UTCEG score recompute
  8. 2026-07-06 04:30 UTCGHSA enrichment
  9. 2026-07-05 16:53 UTCEG score recompute
  10. 2026-07-05 16:53 UTCGHSA enrichment
  11. 2026-07-05 05:16 UTCEG score recompute
  12. 2026-07-05 05:16 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 17:30 UTCEG score recompute
  16. 2026-07-04 17:30 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 05:57 UTCEG score recompute
  19. 2026-07-04 05:57 UTCGHSA enrichment
  20. 2026-07-03 18:18 UTCEG score recompute
  21. 2026-07-03 18:18 UTCGHSA enrichment
  22. 2026-07-03 06:44 UTCEG score recompute
  23. 2026-07-03 06:44 UTCGHSA enrichment
  24. 2026-07-02 19:10 UTCEG score recompute
  25. 2026-07-02 19:10 UTCGHSA enrichment
Show 20 more
  1. 2026-07-02 07:37 UTCEG score recompute
  2. 2026-07-02 07:37 UTCGHSA enrichment
  3. 2026-07-01 20:04 UTCEG score recompute
  4. 2026-07-01 20:04 UTCGHSA enrichment
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-07-01 08:31 UTCEG score recompute▲ 7.80
  7. 2026-07-01 08:31 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  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-28 01:26 UTCEG score recompute
  16. 2026-06-28 01:26 UTCGHSA enrichment
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 18:21 UTCEG score recompute
  20. 2026-06-24 18:02 UTCNVD updatefirst tracked

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 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-53020 actively exploited?
CVE-2026-53020 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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