CVE-2026-53020

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
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

August 5, 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(8)

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

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

(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 5× in last 7d / 85× 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 242 total refreshes for this CVE.

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

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 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-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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53020?
CVE-2026-53020 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

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