arm64: errata: Mitigate TLBI errata on various Arm CPUs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, and 3 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in 925058203229403008d77a52b1e63e2ae5f4a3cf; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in 8364384ae82fbffdf8968abaac3455ed854da18d; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in 7c3ad9365079e716b57d2363d3081ee7680cc18e; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in e717a4d08779f1a28d6e0275e75040b12c33c753; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in 4e7c80742e6dada9f8b9ad63f3a49c03af07ecb8; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in d4fd4282204044fdedd1e42abbe70a9206f74ec0; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in 1b47b1e1d8675fdf5f6e11e7fa19c704d8c6f5cd; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in 1268c64e2bcb6e968152990e87bd10c440fcc9c0; From 58d0ba578bc3b7c044d4ef570307bcb03862cb66 · fixed in cfd391e74134db664feb499d43af286380b10ba8
- Linux Linux
3.7
- KernelLinux
From 3.7.0 · fixed in 5.10.259; From 5.11.0 · fixed in 5.15.210; From 5.16.0 · fixed in 6.1.176; From 6.2.0 · fixed in 6.6.143; From 6.7.0 · fixed in 6.12.94; From 6.13.0 · fixed in 6.18.36; From 6.19.0 · fixed in 7.0.13; From 7.1.0 · fixed in 7.1.1
References 9
git.kernel.org
- stable/c/925058203229403008d77a52b1e63e2ae5f4a3cf
- stable/c/8364384ae82fbffdf8968abaac3455ed854da18d
- stable/c/7c3ad9365079e716b57d2363d3081ee7680cc18e
- stable/c/e717a4d08779f1a28d6e0275e75040b12c33c753
- stable/c/4e7c80742e6dada9f8b9ad63f3a49c03af07ecb8
- stable/c/d4fd4282204044fdedd1e42abbe70a9206f74ec0
- stable/c/1b47b1e1d8675fdf5f6e11e7fa19c704d8c6f5cd
- stable/c/1268c64e2bcb6e968152990e87bd10c440fcc9c0
- stable/c/cfd391e74134db664feb499d43af286380b10ba8