CVE-2026-53354

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 1, 2026

Last Modified

August 17, 2026

Advisory Details (9)

Auto-updated Jul 18, 2026
No patch confirmed yet.
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cfd391e74134db664feb499d43af286380b10ba8
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1268c64e2bcb6e968152990e87bd10c440fcc9c0
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b47b1e1d8675fdf5f6e11e7fa19c704d8c6f5cd
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d4fd4282204044fdedd1e42abbe70a9206f74ec0
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e7c80742e6dada9f8b9ad63f3a49c03af07ecb8
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e717a4d08779f1a28d6e0275e75040b12c33c753
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c3ad9365079e716b57d2363d3081ee7680cc18e
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8364384ae82fbffdf8968abaac3455ed854da18d
generic

arm64: errata: Mitigate TLBI errata on various Arm CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/925058203229403008d77a52b1e63e2ae5f4a3cf

Vendor Advisories for CVE-2026-53354(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

All Vendor Advisories

(3)

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

Frequently asked(5)

What is CVE-2026-53354?
CVE-2026-53354 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-53354 disclosed?
CVE-2026-53354 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53354 actively exploited?
CVE-2026-53354 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 97.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53354?
CVE-2026-53354 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53354?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53354, 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-53354

Explore →

Is Your Infrastructure Affected by CVE-2026-53354?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.