CVE-2026-53020: um: Fix potential race condition in TLB sync

Q: Which Linux environments are most relevant to this issue?

The issue is in the kernel's um component, as indicated by the affected code path. The provided information does not identify specific kernel versions, distributions, or configurations.

Q: What access does an attacker need to exploit this vulnerability?

The severity vector lists local attack access and low privileges, with no user interaction required. The provided data does not describe a specific exploitation method.

Q: What is the impact if exploitation succeeds?

The supplied severity vector indicates high impact to confidentiality, integrity, and availability. This means successful exploitation could affect data disclosure, modification, and system availability.

Q: Is a fix available?

Yes. A patch is available, with stable kernel references provided for the remediation.

Published Jun 24, 2026

Updated

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.

Affected Software

2 affected components

Linux Linux kernel

Linux Linux kernel>=6.19<7.0.10

Remediation

Patch Available

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

Patch Available

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

Event History

Jun 24, 2026

CVE Published

via MITRE·04:29 PM

Data Sourced

via MITRE·04:29 PM

DescriptionSeverity

Data Sourced

via NVD·05:17 PM

RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

Which Linux environments are most relevant to this issue?

The issue is in the kernel's um component, as indicated by the affected code path. The provided information does not identify specific kernel versions, distributions, or configurations.

What access does an attacker need to exploit this vulnerability?

The severity vector lists local attack access and low privileges, with no user interaction required. The provided data does not describe a specific exploitation method.

What is the impact if exploitation succeeds?

The supplied severity vector indicates high impact to confidentiality, integrity, and availability. This means successful exploitation could affect data disclosure, modification, and system availability.

Is a fix available?

Yes. A patch is available, with stable kernel references provided for the remediation.

CVE-2026-53020: um: Fix potential race condition in TLB sync

Affected Software

Remediation

Patch Available

Patch Available

Event History

Frequently Asked Questions

Which Linux environments are most relevant to this issue?

What access does an attacker need to exploit this vulnerability?

What is the impact if exploitation succeeds?

Is a fix available?

Company

Resources

Contact

Frequently Asked Questions

Which Linux environments are most relevant to this issue?

What access does an attacker need to exploit this vulnerability?

What is the impact if exploitation succeeds?

Is a fix available?