In this comprehensive exploration, we delve into the intricate world of Hyper-V, showcasing a collection of significant work and research dedicated to understanding and enhancing the security of Microsoft’s Hyper-V hypervisor.

From detailed proof-of-concept exploits to advanced debugging techniques, this article highlights the critical vulnerabilities discovered and the innovative tools developed for hypervisor research and fuzzing.

Join us as we navigate through the complexities of Hyper-V security, shedding light on its most pivotal aspects.

This repository contains some of the Hyper-V related work I did in the past…


My code from the “Inside Hyper-V” of the Gray Hat Hacking book (6th edition).

Original repository

Includes a framework that can be used to perform hypervisor research/fuzzing and hyper-v specific code (hypercalls, MSRs, VMBus communication).


Windbg script that can be used when debugging hvix64 and provides the following features:

  • Dumping VMCS contents.
  • Dumping EPT tables.
  • GPA -> SPA translation.
  • Conditional breakpoints on VMExit conditions:
    • Use !brexit conditions.
    • Where conditions is a in the form condition1 condition2 .. conditionN.
    • Each condition consists of 3 parts (in the described order and without space between them):
      1. A VMCS field name (for example VM_EXIT_REASON)
      2. condition code: any of ==!=<=>=<>.
      3. An integer value.


Proof of concept for Hyper-V stack overflow bug (hvix64).


Proof of concept for Hyper-V NULL deref bug (hvix64).


Proof of concept for Hyper-V type confusion bug (hvix64).


Proof of concept for Hyper-V arbitrary memory read bug (vmswitch).


  • This bug was classified as RCE, learn why here.
  • This bug has also been presented by other researchers.
  • In the advisory I included other OOB read bugs I found but no CVEs were assigned to them.