Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 743

Meltdown

Reviewed byCybersecurity entrepreneur & security researcher

What is Meltdown?

MeltdownA microarchitectural vulnerability (CVE-2017-5754) that lets unprivileged code read kernel memory by exploiting out-of-order execution and a delayed permission check.


Disclosed on 3 January 2018 by researchers from Google Project Zero, Graz University of Technology, and Cyberus Technology, Meltdown (CVE-2017-5754, "Rogue Data Cache Load") affected most Intel x86 CPUs, IBM POWER, and some ARM cores. It was published alongside the related Spectre flaws, CVE-2017-5753 (bounds-check bypass) and CVE-2017-5715 (branch-target injection).

The defect: a load that violates page-level permissions still forwards its data into transient out-of-order operations before the fault is architecturally raised. A dependent load uses that secret byte to index a probe array, leaving a cache footprint. The attacker then runs Flush+Reload — timing each cache line — and the one that reads back fastest reveals the protected byte. This let a user-mode process dump the entire kernel address space at megabytes per second, defeating KASLR and process isolation.

The primary fix was Kernel Page-Table Isolation (KPTI, originally KAISER), which unmaps kernel pages while in user mode; PCID tagging reduced the TLB-flush overhead. Microcode updates and in-silicon redesigns in later Intel generations (Whiskey Lake, Coffee Lake Refresh) closed the hole in hardware. Meltdown showed how an invisible performance optimisation can become a catastrophic confidentiality failure.

flowchart TD
  A[Unprivileged process] --> B[Load kernel byte<br/>permission check deferred]
  B --> C{Out-of-order execution}
  C -->|transient window| D[Use secret byte to index probe array]
  C -->|fault raised later| E[Access squashed, no architectural read]
  D --> F[One cache line warmed]
  F --> G[Flush+Reload times every line]
  G --> H[Fastest line reveals the secret byte]

● Examples

  1. 01

    Proof-of-concept that dumps kernel memory containing /etc/shadow from an unprivileged process on a vulnerable Intel CPU.

  2. 02

    Cloud providers rolled out KPTI in early 2018 to block cross-tenant kernel reads.

● Frequently asked questions

What is Meltdown?

A microarchitectural vulnerability (CVE-2017-5754) that lets unprivileged code read kernel memory by exploiting out-of-order execution and a delayed permission check. It belongs to the Vulnerabilities category of cybersecurity.

What does Meltdown mean?

A microarchitectural vulnerability (CVE-2017-5754) that lets unprivileged code read kernel memory by exploiting out-of-order execution and a delayed permission check.

How do you defend against Meltdown?

Defences for Meltdown typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for Meltdown?

Common alternative names include: Rogue Data Cache Load, CVE-2017-5754.

● Related terms

● See also