Divide et Impera: MemoryRanger Runs Drivers in Isolated Kernel Spaces
summary
MemoryRanger claims to stop driver code-dumps, data theft and PROCESS privilege escalation by running each third-party driver in per-driver EPT enclaves implemented on Intel VT-x / EPT; illegal reads/writes trigger EPT violations, the hypervisor swaps PFNs to redirect PFN to fake pages and returns fake data while restoring the real page afterward. Prototype isolates three test drivers, prevents dumping and data tampering, blocks an attempted privilege escalation, runs ~3× faster than a closest EPT-only competitor, but is a proof‑of‑concept that doesn’t yet handle preloaded drivers or coexisting Hyper‑V.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:27The threat of kernel attacks
- 3:24Demonstration of memory theft
- 7:32Privilege escalation demo
- 10:53Existing security limitations
- 12:20Virtualization and EPT
- 15:14Memory Ranger design
- 19:16Memory Ranger demo
- 28:17Architecture summary
- 31:19Implementation steps
- 33:53Benchmarks and conclusion
- 36:24Q&A and final demo
related talks
01h 03mret2dir: Deconstructing Kernel Isolation
53mXenpwn: Breaking Paravirtualized Devices
18mGuest Memory Protection -- Current Status and Future
24mShielding Software From Privileged Side-Channel Attacks
30mMicro-Virtualization Memory Tracing to Detect and Prevent Spraying Attacks
25mHigh Performance VM Introspection
48mNext Level Cheating and Leveling Up Mitigations
32mSeeing Through The Same Lens...
