CVE-2026-63875

arm64: tlb: Flush walk cache when unsharing PMD tables

HIGH
7.8
CVSS Score
Published: July 19, 2026 at 02:54 PM UTC
Updated: October 30, 2026 at 02:57 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
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: arm64: tlb: Flush walk cache when unsharing PMD tables When huge_pmd_unshare() is called to unshare a PMD table, the tlb_unshare_pmd_ptdesc() function sets tlb->unshared_tables=true but the aarch64 tlb_flush() only checked tlb->freed_tables to determine whether to use TLBF_NONE (vae1is, invalidates walk cache) or TLBF_NOWALKCACHE (vale1is, leaf-only). This caused the stale PMD page table entry to remain in the walk cache after unshare, potentially leading to incorrect page table walks. Fix by including unshared_tables in the check, so that when unsharing tables, TLBF_NONE is used and the walk cache is properly invalidated. Here is the detailed distinction between vae1is and vale1is: | Instruction Combination | Actual Invalidation Scope | | ------------------------ | --------------------------------------------------| | `VAE1IS` + TTL=`0` | All entries at all levels (full invalidation) | | `VAE1IS` + TTL=`2` (L2) | Non-leaf at Level 0/1 + leaf at Level 2 | | `VALE1IS` + TTL=`0` | Leaf entries at all levels (non-leaf not cleared) | | `VALE1IS` + TTL=`2` (L2) | Leaf entry at Level 2 only |

Affected

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

5.10.253 ≤ v < 5.10.2595.15.203 ≤ v < 5.15.2106.1.167 ≤ v < 6.1.1766.12.74 ≤ v < 6.12.936.18.13 ≤ v < 6.18.356.19.1 ≤ v < 7.0.126.6.127 ≤ v < 6.6.1435.10.2535.15.2036.1.1676.12.746.18.136.196.6.1276495204f8219a57859669d618b25d06176d5a8727.18ce720d5bd91e9dc16db3604aa4b1bf76770a9a19b671f6f432be07c0ddd66e437d6d0e0db684f83ce4cf24761467756462c0e1dbe4a5e9c9eb520fcda06bb0ca45b1ca6f1ab55023e34e61a520337f3daa6707b71a2da23a82979fa21f788aeb706f1a2ff37dd18ce7739a26aab0cc2d31006a45e6bde63
Vendor states this is fixed in 0199c9d57861f17b556b6cba1f765c7cce79745b (fixed)
Vendor states this is fixed in 47490bbb05c8c0e09cc3cfd237d8934ffc340583 (fixed)
Vendor states this is fixed in 48125cd9c55cbe297b59fd1f9bda48b0960bd181 (fixed)
Vendor states this is fixed in 8ca7284da0e67b3e71d90ec17f08286774245ad9 (fixed)
Vendor states this is fixed in c2ff4764e03e7a8d758352f4aceb8fe1be6ac971 (fixed)
Vendor states this is fixed in d766a49d9b55705c4737cd8bb5d3faa2d31330fd (fixed)
Vendor states this is fixed in dced308d7d6a0de1c09d2058f38f1aaaf5cbb914 (fixed)
Vendor states this is fixed in fe93e907b1af03cc229a80aa64a570a103d2b279 (fixed)
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.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.19 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

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

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusANALYZED
CWE
CWE-459CWE-670

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