CVE-2026-53354: arm64: errata: Mitigate TLBI errata on various Arm CPUs

Published Jul 1, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

Affected Software

12 affected componentsFixes available
Linux Kernel
Microsoft azl3 kernel 6.6.143.1-1
Linux Linux kernel>=3.7<5.10.259
Linux Linux kernel>=5.11<5.15.210
Linux Linux kernel>=5.16<6.1.176
Linux Linux kernel>=6.2<6.6.143
Linux Linux kernel>=6.7<6.12.94
Linux Linux kernel>=6.13<6.18.36
Linux Linux kernel>=6.19<7.0.13
Linux Linux kernel>=7.1<7.1.1
debian/linux<=5.10.223-1
5.10.262-16.1.176-16.1.180-16.12.94-16.12.101-17.1.7-17.1.8-1
debian/linux-6.1
6.1.180-1~deb11u1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.7-1Fixed in 7.1.8-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.180-1~deb11u1
  3. Configuration

    Enable the ARM64_WORKAROUND_REPEAT_TLBI workaround on affected Arm CPUs to mitigate the TLBI errata (arm64: errata: Mitigate TLBI errata on various Arm CPUs).

    Linux kernel (arm64) ARM64_WORKAROUND_REPEAT_TLBI = enable
  4. Configuration

    For any affected TLBI;DSB sequence, append an additional TLBI;DSB (the additional TLBI can use any operation broadcast to affected CPUs; the additional DSB can use any option sufficient to complete the additional TLBI) so that all memory write effects affected by the first TLBI are globally observed.

    Software/firmware sequence (TLBI;DSB) additional TLBI;DSB = add after affected sequence
  5. Compensating control

    Update the silicon errata documentation accordingly for the affected CPUs (including any CPUs that share a common erratum number) so the required workaround/sequence is reflected in the documentation.

Event History

Jul 1, 2026
CVE Published
via MITRE·01:32 PM
Data Sourced
via MITRE·01:32 PM
DescriptionSeverity
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 2, 2026
Data Sourced
via Microsoft·08:03 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-53354?

CVE-2026-53354 has a risk rating of 26, indicating a significant impact depending on the affected configurations.

2

What types of CPUs are affected by CVE-2026-53354?

CVE-2026-53354 affects various Arm CPUs that have specific errata related to TLBI handling.

3

How do I fix CVE-2026-53354?

To mitigate CVE-2026-53354, ensure you are using an updated version of the Linux kernel that includes the relevant patches for TLBI errata.

4

What is the main issue addressed by CVE-2026-53354?

CVE-2026-53354 addresses an issue where a broadcast TLBI;DSB sequence may complete incorrectly on affected Arm CPUs.

5

When was CVE-2026-53354 published?

CVE-2026-53354 was published on July 1, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203