~/talk

Meltdown: Reading Kernel Memory from User Space

Talkat USENIX Security '18 · on Thursday, 2018-08-16· at 16:30· Grand Ballroom 1-4· [security]
slides:none on file

Meltdown demonstrates that out of order execution leaks kernel memory by executing transient instructions that encode secret bytes into the cache and recovering them with a Flush+Reload cache side channel. It reads arbitrary physical memory, achieving about 582 KB/s when data hits L1, ~12.4 KB/s from L3 and only ~10 B/s for uncached lines (an improved method reaches ~3.2 KB/s). Mitigations include KAISER / KPTI; Intel CPUs are broadly affected, AMD mostly not, Apple devices are affected.

AI-written summary · about

  1. 0:00Intro
  2. 0:24Kernel addresses
  3. 1:20Paging
  4. 2:39Architecture
  5. 4:10CPU Cache
  6. 6:10Out of Order Execution
  7. 7:27Toy Example
  8. 8:08Building Blocks
  9. 9:45Fault Handling
  10. 10:32Cover Channel
  11. 10:58Cache Attack
  12. 11:58Meltdown Attack
  13. 12:46New Experiment
  14. 13:23Uncatchable Memory
  15. 14:04Who is affected
  16. 14:34Exynos Mongoose
  17. 15:39Breaking the SLR
  18. 16:34Locating a victim process
  19. 17:05Using the physical address
  20. 17:36Fixing the hardware
  21. 18:14Kaiser
  22. 19:56Conclusion
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.