KPTI / Meltdown implications

TL;DR: Meltdown (CVE-2017-5754) let unprivileged code read kernel memory via speculative loads through the user page table; Kernel Page Table Isolation (KPTI / KVA Shadow on Windows) splits kernel/user page tables so user mode has no virtual mapping of kernel memory to speculate against.

What it is

Meltdown exploited Intel CPUs that performed permission checks late in the load pipeline: a faulting load from a kernel address transiently produced data the attacker could measure via a cache side channel before the fault retired. The defence is structural — give user mode a page table that does not map the kernel, so there is no kernel virtual address to speculatively load. Windows ships this as “KVA Shadow”; Linux as KPTI/PTI; macOS as Double Map.

Preconditions / where it applies

Intel CPUs prior to Coffee Lake-R/Whiskey Lake (vulnerable to Meltdown); AMD generally unaffected by Meltdown specifically
Windows 10 1709+ enables KVA Shadow automatically on vulnerable CPUs; check via Get-SpeculationControlSettings
Newer CPUs report MELTDOWN_NO/RDCL_NO in CPUID and skip the shadow tables (perf win)

Technique

What KPTI/KVA Shadow does:

User and kernel each get their own PML4; SYSCALL/SYSRET swap CR3 across the boundary
A small “trampoline” page maps both in user-page-table form so the CPU can enter the kernel before the swap completes
Cost: extra TLB flushes on every transition; PCID/ASID hardware mitigates the worst of it

What changed for exploit authors:

Meltdown itself is dead on patched + KVA-Shadow systems
EntryBleed (2022) — researchers showed that on KPTI systems, the trampoline page’s TLB residency leaks kernel function offsets through prefetch timing → renewed kaslr-bypass primitive
Spectre v1/v2/L1TF — separate side channels, not addressed by KPTI; mitigated by IBRS/IBPB/STIBP and L1D flush on context switch
Newer transient-execution attacks (Downfall, Inception, RetBleed) — informational anchor: each generation closes specific gadgets, and Windows ships per-CPU mitigations enabled by default on affected hardware

PowerShell sanity check:
  Get-SpeculationControlSettings
Output highlights:
  Hardware requires kernel VA shadowing: True/False
  Windows OS support for kernel VA shadow is enabled: True

Detection and defence

Keep Windows up to date — Microsoft pushes microcode and OS mitigations via Windows Update; bcdedit flags can disable them, hunt for tamper
For exploit dev: expect Meltdown-class leaks to fail on modern hosts; pivot KASLR strategy to logic leaks (see uninitialised-memory-disclosures, kaslr-bypass)
Server roles handling untrusted code (hypervisors, multi-tenant containers) should enable HVCI (hvci-vbs) and verify mitigation registry keys
Performance trade-off: PCID-enabled CPUs absorb KPTI cost cheaply; disable shadow tables only on attested-safe CPUs

References

Meltdown paper (Lipp et al., USENIX 2018) — original disclosure
Microsoft: KVA Shadow (Windows internals blog) — implementation notes
EntryBleed writeup — KPTI-side-channel KASLR break