CVE-2026-53354

arm64: errata: Mitigate TLBI errata on various Arm CPUs

HIGH
8.8
CVSS Score
Published: July 1, 2026 at 01:32 PM UTC
Updated: October 19, 2026 at 08:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: arm64: errata: Mitigate TLBI errata on various Arm CPUs A number of CPUs developed by Arm suffer from errata whereby a broadcast TLBI;DSB sequence may complete before the global observation of writes which are translated by an affected TLB entry. These errata ONLY affect the completion of memory accesses which have been translated by an invalidated TLB entry, and these errata DO NOT affect the actual invalidation of TLB entries. TLB entries are removed correctly. This issue has been assigned CVE ID CVE-2025-10263. To mitigate this issue, Arm recommends that software follows any affected TLBI;DSB sequence with an additional TLBI;DSB, which will ensure that all memory write effects affected by the first TLBI have been globally observed. The additional TLBI can use any operation that is broadcast to affected CPUs, and the additional DSB can use any option that is sufficient to complete the additional TLBI. The ARM64_WORKAROUND_REPEAT_TLBI workaround is sufficient to mitigate the issue. Enable this workaround for affected CPUs, and update the silicon errata documentation accordingly. Note that due to the manner in which Arm develops IP and tracks errata, some CPUs share a common erratum number.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.7 ≤ v < 5.10.2595.11 ≤ v < 5.15.2105.16 ≤ v < 6.1.1766.13 ≤ v < 6.18.366.19 ≤ v < 7.0.136.2 ≤ v < 6.6.1436.7 ≤ v < 6.12.947.1 ≤ v < 7.1.13.758d0ba578bc3b7c044d4ef570307bcb03862cb66
Vendor states this is fixed in 1268c64e2bcb6e968152990e87bd10c440fcc9c0 (fixed)
Vendor states this is fixed in 1b47b1e1d8675fdf5f6e11e7fa19c704d8c6f5cd (fixed)
Vendor states this is fixed in 4e7c80742e6dada9f8b9ad63f3a49c03af07ecb8 (fixed)
Vendor states this is fixed in 7c3ad9365079e716b57d2363d3081ee7680cc18e (fixed)
Vendor states this is fixed in 8364384ae82fbffdf8968abaac3455ed854da18d (fixed)
Vendor states this is fixed in 925058203229403008d77a52b1e63e2ae5f4a3cf (fixed)
Vendor states this is fixed in cfd391e74134db664feb499d43af286380b10ba8 (fixed)
Vendor states this is fixed in d4fd4282204044fdedd1e42abbe70a9206f74ec0 (fixed)
Vendor states this is fixed in e717a4d08779f1a28d6e0275e75040b12c33c753 (fixed)
Vendor states this is fixed in 3.7 (unaffected)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 5.15.210 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.94 (unaffected)
Vendor states this is fixed in 6.18.36 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.13 (unaffected)
Vendor states this is fixed in 7.1.1 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card