A systematic collection of research papers on hypervisor testing and fuzzing, including virtual device testing, vCPU emulation, hypercall interfaces, and nested virtualization. This repository accompanies our survey paper "Hypervisor Testing: Techniques, Challenges, and Future Directions". Feel free to make contributions by creating pull requests.
We followed a rigorous literature review protocol adapted from Kitchenham's guidelines:
Database Search: ACM Digital Library, IEEE Xplore, USENIX, DBLP, Semantic Scholar
Search Query:
("Hypervisor" OR "VMM" OR "QEMU" OR "KVM" OR "Xen" OR "Hyper-V" OR "VirtualBox" OR "Virtual Device")
AND ("Fuzzing" OR "Fuzz Testing" OR "Security Testing" OR "Vulnerability Detection" OR "Symbolic Execution")
Venue Filter: Top-tier security (S&P, USENIX Security, CCS, NDSS), systems (OSDI, SOSP, EuroSys, ATC), and software engineering (ICSE, FSE, ASE) conferences.
Snowballing: Backward (references) and forward (Google Scholar citations) until saturation.
Tool Collection: GitHub search with star ranking and activity filtering.
2026 | 2025 | 2024 | 2023 | 2022 | 2021 | 2020 | 2017
Virtual Device Testing | vCPU Emulation Testing | Hypercall and VM-Exit Testing | Nested Virtualization Testing
Coverage-Guided Fuzzing | Grammar and Dependency-Aware Fuzzing | DMA-Centric Approaches | Hybrid Fuzzing with Symbolic Execution | Trace-Based and Replay Approaches | Universal and Black-Box Approaches | Fault Injection and Robustness Assessment
- NecoFuzz: Effective Fuzzing of Nested Virtualization via Fuzz-Harness Virtual Machines [pdf]
- Authors: Ishii, Fukai, Shinagawa (University of Tokyo; Fukai at AIST)
- Target: KVM, Xen, VirtualBox (Nested Virtualization)
- Findings: 6 vulnerabilities, all confirmed by maintainers; 2 CVEs (CVE-2023-30456, CVE-2024-21106)
- HyperMirage: Direct State Manipulation in Hybrid Virtual CPU Fuzzing [pdf]
- Authors: Andreas, Specht, Momeu (Technical University of Munich)
- Target: Xen and KVM (vCPU emulation, Intel x86)
- Findings: 11 new bugs (9 Xen, 2 KVM), all confirmed by maintainers; CVE assignment per paper PDF (e.g., CVE-2023-46842 mentioned by secondary sources, awaiting primary-source confirmation)
- Truman: Constructing Device Behavior Models from OS Drivers to Fuzz Virtual Devices [pdf]
- Authors: Ma et al.
- Target: QEMU, VirtualBox, VMware Workstation Pro, Parallels
- Findings: 54 new bugs, 6 CVEs
- InSVDF: Interface-State-Aware Virtual Device Fuzzing [pdf]
- Authors: Zhang et al.
- Target: QEMU
- Findings: 2 new vulnerabilities, 1 CVE
- COSMOS: A Fault Injection Framework to Assess Hardware-Assisted Hypervisors [pdf]
- Authors: Cinque et al. (Federico II University of Naples)
- Target: KVM, Xen, Jailhouse (hardware-assisted hypervisors via nested virtualization)
- Technique: Fault injection, no target instrumentation required
- Findings: Non-negligible non-fail-stop behaviors; notable differences across hypervisors in failure logging and recovery
- GitHub: https://github.com/dessertlab/Cosmos
- HYPERPILL: Fuzzing for Hypervisor-bugs by Leveraging the Hardware Virtualization Interface [pdf]
- Authors: Bulekov, Liu, Egele, Payer (EPFL, Boston University, Zhejiang University)
- Target: QEMU/KVM, Microsoft Hyper-V, macOS Virtualization Framework (universal approach via hardware virtualization interface)
- Findings: 26 new bugs (11 in QEMU), 9 CVEs
- ViDeZZo: Dependency-aware Virtual Device Fuzzing [pdf]
- Authors: Qiang Liu et al. (Zhejiang University, EPFL HexHive)
- Target: QEMU, VirtualBox (28 virtual devices across 4 architectures)
- Findings: 28 new bugs, 7 patches accepted upstream, 1 CVE assigned at publication (24 prior bugs reproduced as comparison baselines, not counted as new discoveries)
- VD-Guard: DMA Guided Fuzzing for Hypervisor Virtual Device [pdf]
- Authors: Yuwei Liu et al. (Institute of Software CAS, SJTU; distinct from ViDeZZo's lead author)
- Target: QEMU, VirtualBox
- Findings: 4 new vulnerabilities, all confirmed and fixed, 3 CVEs
- IRIS: A Record and Replay Framework to Enable Hardware-assisted Virtualization Fuzzing [pdf]
- Authors: Cesarano et al. (Federico II University of Naples)
- Target: Xen hypervisor
- GitHub: https://github.com/dessertlab/iris
-
Morphuzz: Bending (Input) Space to Fuzz Virtual Devices [pdf]
- Authors: Bulekov et al. (Boston University, Red Hat)
- Target: QEMU, bhyve
- Findings: 66 new bugs (61 QEMU + 5 bhyve), 22 fixes accepted, 9 CVEs
-
MundoFuzz: Hypervisor Fuzzing with Statistical Coverage Testing and Grammar Inference [pdf]
- Authors: Myung et al. (Seoul National University)
- Target: QEMU, bhyve
- Findings: 40 previously unknown bugs (23 QEMU + 17 bhyve), 9 CVEs
- Nyx-Net: Network Fuzzing with Incremental Snapshots [pdf]
- Authors: Schumilo et al.
- Target: Network services (extends Nyx framework)
- Findings: Bugs in Lighttpd, MySQL client, Firefox IPC
- Nyx: Greybox Hypervisor Fuzzing using Fast Snapshots and Affine Types [pdf]
- Authors: Schumilo et al. (Ruhr-Universität Bochum)
- Target: QEMU/KVM, bhyve
- Findings: 44 new bugs, 22 CVEs requested
-
V-Shuttle: Scalable and Semantics-Aware Hypervisor Virtual Device Fuzzing [pdf]
- Authors: Pan et al.
- Target: QEMU, VirtualBox
- Findings: 35 new bugs, 17 CVEs
-
HyperFuzzer: An Efficient Hybrid Fuzzer for Virtual CPUs [pdf]
- Authors: Ge et al. (Microsoft Research, Microsoft, Penn State, Facebook, KAIST)
- Target: Microsoft Hyper-V (vCPU emulation)
- Findings: 11 previously unknown bugs, all confirmed and fixed (6 security-critical)
- hAFL1: Our Journey of Fuzzing Hyper-V and Discovering a Critical 0-Day [slides]
- Authors: Harpaz & Hadar (Guardicore, SafeBreach)
- Target: Microsoft Hyper-V (vmswitch.sys)
- Findings: CVE-2021-28476 (CVSS 9.9)
- Follow-on tooling: hAFL2, the open-sourced, nested-VM-capable kAFL-based Hyper-V VSP fuzzer released alongside the talk
- Hyntrospect: A Coverage-Guided Fuzzer for Hyper-V Emulated Devices [paper] [slides]
- Authors: Dubois (Google; work performed in collaboration with the Project Zero team, per the SSTIC paper). Also presented at BlueHat IL 2022.
- Target: Microsoft Hyper-V emulated devices in the root-partition userland (port I/O guest interface)
- Technique: Coverage-guided fuzzing of closed-source binaries, Hyper-V checkpoints for per-input state reset
- Findings: No security vulnerabilities reported in the SSTIC 2021 campaign (one non-security guest-VM crash in i8042 reported to MSRC)
- GitHub: https://github.com/googleprojectzero/Hyntrospect
- HYPER-CUBE: High-Dimensional Hypervisor Fuzzing [pdf]
- Authors: Schumilo et al. (Ruhr-Universität Bochum)
- Target: Six hypervisors — QEMU/KVM, VirtualBox, VMware Fusion, Intel ACRN, bhyve, Parallels
- Findings: 54 novel bugs, 43 CVEs
- VDF: Targeted Evolutionary Fuzz Testing of Virtual Devices [pdf]
- Authors: Henderson et al.
- Target: QEMU
Virtual devices are the primary attack surface of hypervisors, exposing interfaces for MMIO/PIO operations, DMA transfers, and interrupt handling.
- HYPER-CUBE: High-Dimensional Hypervisor Fuzzing (NDSS '20) [pdf]
- Nyx: Greybox Hypervisor Fuzzing using Fast Snapshots and Affine Types (USENIX Security '21) [pdf]
- V-Shuttle: Scalable and Semantics-Aware Hypervisor Virtual Device Fuzzing (CCS '21) [pdf]
- hAFL1: Our Journey of Fuzzing Hyper-V and Discovering a Critical 0-Day (Black Hat USA '21)
- Hyntrospect: A Coverage-Guided Fuzzer for Hyper-V Emulated Devices (SSTIC '21) [paper]
- Morphuzz: Bending (Input) Space to Fuzz Virtual Devices (USENIX Security '22) [pdf]
- ViDeZZo: Dependency-aware Virtual Device Fuzzing (S&P '23) [pdf]
- VD-Guard: DMA Guided Fuzzing for Hypervisor Virtual Device (ASE '23) [pdf]
- Truman: Constructing Device Behavior Models from OS Drivers to Fuzz Virtual Devices (NDSS '25) [pdf]
- InSVDF: Interface-State-Aware Virtual Device Fuzzing (ICSE '25) [pdf]
- VDF: Targeted Evolutionary Fuzz Testing of Virtual Devices (RAID '17) [pdf]
vCPU emulation involves instruction decoding, operand handling, privilege checks, and exception injection. Vulnerabilities can cause incorrect guest execution or enable guest-to-host escape.
- HyperFuzzer: An Efficient Hybrid Fuzzer for Virtual CPUs (CCS '21) [pdf]
- HyperMirage: Direct State Manipulation in Hybrid Virtual CPU Fuzzing (NDSS '26)
Hypercalls provide a direct interface for guest-to-hypervisor communication, while VM-exits transfer control to the hypervisor for privileged operations.
- MundoFuzz: Hypervisor Fuzzing with Statistical Coverage Testing and Grammar Inference (USENIX Security '22) [pdf]
- HYPERPILL: Fuzzing for Hypervisor-bugs by Leveraging the Hardware Virtualization Interface (USENIX Security '24) [pdf]
Nested virtualization enables running hypervisors inside VMs, introducing additional complexity in VMCS shadowing, nested page table management, and VM-exit handling.
- IRIS: A Record and Replay Framework to Enable Hardware-assisted Virtualization Fuzzing (DSN '23) [pdf]
- NecoFuzz: Effective Fuzzing of Nested Virtualization via Fuzz-Harness Virtual Machines (EuroSys '26) [pdf]
Approaches that use code coverage feedback to guide input generation and explore new execution paths.
- HYPER-CUBE: High-Dimensional Hypervisor Fuzzing (NDSS '20) [pdf]
- Nyx: Greybox Hypervisor Fuzzing using Fast Snapshots and Affine Types (USENIX Security '21) [pdf]
- Nyx-Net: Network Fuzzing with Incremental Snapshots (EuroSys '22) [pdf]
- MundoFuzz: Hypervisor Fuzzing with Statistical Coverage Testing and Grammar Inference (USENIX Security '22) [pdf]
- Hyntrospect: A Coverage-Guided Fuzzer for Hyper-V Emulated Devices (SSTIC '21) [paper]
- hAFL1: Our Journey of Fuzzing Hyper-V and Discovering a Critical 0-Day (Black Hat USA '21) - kAFL-based coverage-guided fuzzer for Hyper-V VSPs
Approaches that leverage protocol specifications, message dependencies, or device behavior models to generate semantically valid inputs.
- V-Shuttle: Scalable and Semantics-Aware Hypervisor Virtual Device Fuzzing (CCS '21) [pdf]
- ViDeZZo: Dependency-aware Virtual Device Fuzzing (S&P '23) [pdf]
- MundoFuzz: Hypervisor Fuzzing with Statistical Coverage Testing and Grammar Inference (USENIX Security '22) [pdf]
- Truman: Constructing Device Behavior Models from OS Drivers to Fuzz Virtual Devices (NDSS '25) [pdf]
Approaches that specifically target DMA (Direct Memory Access) handling in virtual devices.
- Morphuzz: Bending (Input) Space to Fuzz Virtual Devices (USENIX Security '22) [pdf]
- VD-Guard: DMA Guided Fuzzing for Hypervisor Virtual Device (ASE '23) [pdf]
- InSVDF: Interface-State-Aware Virtual Device Fuzzing (ICSE '25) [pdf]
Approaches that combine fuzzing with symbolic execution to systematically explore complex code paths.
- HyperFuzzer: An Efficient Hybrid Fuzzer for Virtual CPUs (CCS '21) [pdf]
- Uses "Nimble Symbolic Execution" with Intel PT for efficient vCPU testing
Approaches that use execution traces or record-and-replay mechanisms.
- VDF: Targeted Evolutionary Fuzz Testing of Virtual Devices (RAID '17) [pdf]
- IRIS: A Record and Replay Framework to Enable Hardware-assisted Virtualization Fuzzing (DSN '23) [pdf]
Approaches designed to work across multiple hypervisors without requiring source code access or hypervisor-specific modifications.
- HYPERPILL: Fuzzing for Hypervisor-bugs by Leveraging the Hardware Virtualization Interface (USENIX Security '24) [pdf]
- NecoFuzz: Effective Fuzzing of Nested Virtualization via Fuzz-Harness Virtual Machines (EuroSys '26)[pdf]
- COSMOS: A Fault Injection Framework to Assess Hardware-Assisted Hypervisors (TDSC '25) [pdf]
Approaches that inject faults (transient hardware faults, error conditions) into the hypervisor to assess robustness, fail-stop behavior, error logging, and recovery.
- COSMOS: A Fault Injection Framework to Assess Hardware-Assisted Hypervisors (TDSC '25) [pdf]
- Uses nested virtualization to inject faults into KVM, Xen, and Jailhouse without target instrumentation
| Hypervisor | Papers |
|---|---|
| QEMU/KVM | HYPER-CUBE, Nyx, Morphuzz, MundoFuzz, V-Shuttle, ViDeZZo, VD-Guard, HYPERPILL, Truman, InSVDF, VDF, NecoFuzz, HyperMirage, COSMOS |
| VirtualBox | HYPER-CUBE, V-Shuttle, ViDeZZo, VD-Guard, Truman, NecoFuzz |
| Hyper-V | HyperFuzzer, hAFL1, Hyntrospect, HYPERPILL |
| Xen | IRIS, NecoFuzz, HyperMirage, COSMOS |
| VMware | HYPER-CUBE (Fusion), Truman (Workstation Pro) |
| macOS Virtualization Framework | HYPERPILL |
| bhyve | HYPER-CUBE, Nyx, Morphuzz, MundoFuzz |
| ACRN | HYPER-CUBE |
| Parallels | HYPER-CUBE, Truman |
| Jailhouse | COSMOS |
All counts below are taken from the abstract/introduction of each paper. Where the paper distinguishes "patches accepted" from "CVEs assigned", we report both; CVE assignment often lags publication. Hyntrospect is omitted because its SSTIC 2021 campaign reported no security findings.
| Tool | Venue | New Bugs | CVEs |
|---|---|---|---|
| HYPER-CUBE | NDSS '20 | 54 | 43 |
| Nyx | USENIX Sec. '21 | 44 | 22 requested |
| V-Shuttle | CCS '21 | 35 | 17 |
| HyperFuzzer | CCS '21 | 11 (6 security-critical) | not disclosed |
| hAFL1 | Black Hat '21 | 1 | 1 (CVE-2021-28476, CVSS 9.9) |
| Morphuzz | USENIX Sec. '22 | 66 (61 QEMU + 5 bhyve) | 9 (22 fixes accepted) |
| MundoFuzz | USENIX Sec. '22 | 40 (23 QEMU + 17 bhyve) | 9 |
| ViDeZZo | S&P '23 | 28 | 7 patches accepted; 1 CVE at publication |
| VD-Guard | ASE '23 | 4 | 3 |
| HYPERPILL | USENIX Sec. '24 | 26 (11 QEMU + others in Hyper-V, macOS VF) | 9 |
| Truman | NDSS '25 | 54 | 6 |
| InSVDF | ICSE '25 | 2 | 1 |
| HyperMirage | NDSS '26 | 11 (9 Xen + 2 KVM) | confirmed by maintainers; specific CVE IDs to be verified from full PDF |
| NecoFuzz | EuroSys '26 | 6 | 2 (CVE-2023-30456, CVE-2024-21106) |
| Tool | Repository | Status |
|---|---|---|
| HYPER-CUBE | RUB-SysSec/hypercube | Available |
| Nyx | nyx-fuzz/Nyx | Available |
| Morphuzz | QEMU upstream | Merged |
| V-Shuttle | hustdebug/v-shuttle | Available |
| ViDeZZo | HexHive/ViDeZZo | Available |
| IRIS | dessertlab/iris | Available |
| Truman | truman | Available |
| COSMOS | dessertlab/Cosmos | Available |
| Hyntrospect | googleprojectzero/Hyntrospect | Available |
| hAFL2 | SafeBreach-Labs/hAFL2 | Available |
- kAFL: Hardware-Assisted Feedback Fuzzing for OS Kernels (USENIX Security '17) [pdf] - Foundation for many hypervisor fuzzers
- AFL: American Fuzzy Lop - Core mutation strategies used by many tools
- Intel PT: Hardware tracing used for coverage feedback
We propose a unified taxonomy for classifying hypervisor testing techniques. Each dimension represents an orthogonal design axis.
| Dimension | Question | Options |
|---|---|---|
| D1: Target | What component is tested? | Virtual devices, Hypercalls/VM-exits, vCPU emulation, Core subsystems |
| D2: Input Model | What is the input abstraction? | Raw bytes, Structured messages, I/O op sequences, Instruction+CPU state, Full VM state |
| D3: Input Source | Where do seeds come from? | Pattern/random, Trace-based, Specification-based, Inference-based, Driver-derived |
| D4: Instrumentation | How is execution observed? | Compile-time, Hardware tracing (Intel PT), Dynamic binary instrumentation, Emulation-based |
| D5: Feedback | What signals guide fuzzing? | Code coverage, State coverage, Interface coverage, Differential/semantic, Hybrid |
| D6: Execution & Reset | How is state managed? | VM snapshot, Fork-based (CoW), Full reboot, Nested virtualization |
| D7: Oracle | What counts as a bug? | Crash/hang, Sanitizers, Invariant violation, Differential divergence |
Four fundamental trade-offs govern hypervisor testing tool design:
- Universal fuzzers (HyperPill): Work across multiple hypervisors but achieve shallower testing
- Specialized fuzzers (V-Shuttle, HyperFuzzer): Achieve deeper testing through target-specific optimizations
- Principle: Start broad, go deep - use universal approaches for initial assessment, then specialize
- Richer input models (grammar-based, driver-derived): More valid inputs but higher generation overhead
- Simpler models (raw bytes): Higher throughput but more invalid inputs rejected by parsers
- Principle: Match input complexity to protocol complexity
- Maximum observability (emulation-based): 10-100x overhead but universal support
- Hardware tracing (Intel PT): <5% overhead but requires specific hardware
- Principle: Use minimum sufficient instrumentation
- Fork-based (Morphuzz, ViDeZZo): Sub-millisecond reset but only user-space state
- Snapshot-based (NYX): 1-10ms reset with full VM state isolation
- Principle: Isolate what matters - fork for device fuzzing, snapshot for cross-device testing
| Challenge | Current Limitation | Potential Approach |
|---|---|---|
| State Space Explosion | Exponential growth in device states | Abstract interpretation, state hashing |
| Semantic Validity | Manual specification effort doesn't scale | LLM-assisted inference, driver analysis |
| Coverage Noise | Non-deterministic signals from interrupts/timers | Statistical filtering, deterministic replay |
| Cross-Platform Portability | Architecture-specific tools (x86-centric) | Hardware interface abstraction |
| Scalable Triage | Manual crash analysis at scale | Automated root cause clustering |
| Emerging Architectures | Limited ARM/RISC-V support | ARM CoreSight, portable frameworks |
Papers are counted by their primary attack-surface target as listed in Papers by Testing Target. A paper that crosses targets (e.g., HYPER-CUBE, HYPERPILL) is counted under its primary contribution.
| Attack Surface | Papers | Gap Analysis |
|---|---|---|
| Virtual Devices | 11/18 (61%) | Well-studied for legacy/MMIO devices; complex stateful protocols (NVMe, virtio-gpu, virtio-net offloads) remain underexplored |
| vCPU Emulation | 2/18 (11%) | Severely underexplored - extension instruction sets (AVX-512, SGX/TDX, AMX) untested |
| Hypercalls/VM-Exit | 2/18 (11%) | Severely underexplored - systematic hypercall sequence and VM-exit handler testing missing |
| Nested Virtualization | 2/18 (11%) | Emerging area; VMCS shadowing, nested EPT, and L2->L0 escape paths under-tested |
| Fault Injection / Robustness | 1/18 (6%) | Almost unexplored; only COSMOS targets non-fail-stop behavior and recovery |
| Core Subsystems (MMU, scheduler, IOMMU, IPC) | 0/18 (0%) | No dedicated study; touched only as side effects of other fuzzers |
Reporting weaknesses we observed while extracting comparable evaluation data across the surveyed papers. The exact frequencies are not given here because the per-paper coding is methodologically subjective (e.g., what counts as "missing" baseline); the issues themselves recur frequently enough to warrant explicit guidance.
| Pitfall | Recommendation |
|---|---|
| Throughput reported without coverage context | Report effective coverage rate (edges/sec or new-edges/sec) alongside raw exec/sec |
| Device count reported without complexity classification | Classify devices by complexity (simple/medium/complex), e.g., MMIO-only vs. DMA+state-machine |
| CVE count reported without severity or deduplication policy | Report bugs with root cause and CVSS severity; state how duplicates were detected |
| Snapshot configuration details omitted | Specify guest memory size, snapshot timing, enabled devices |
| Non-standardized time budgets | Provide at least two budgets (e.g., 1h and 24h) to allow comparison |
| Missing or inadequate baselines | Compare against at least one prior tool on the same target and budget |
| Category | Required Information |
|---|---|
| Target | Hypervisor name/version; device list with complexity; commit hash |
| Configuration | Guest memory size; snapshot timing; enabled devices; instrumentation flags |
| Metrics | Edge coverage over time; throughput with context; per-device breakdown |
| Bugs | Deduplication method; root cause classification; severity (CVSS) |
| Reproducibility | Seeds and configurations; Docker/VM image; expected coverage range |
| Baselines | At least one prior tool on same targets/budget |
| Statistics | Multiple runs (>=5); mean and variance; significance tests |
Contributions are welcome:
- Adding new papers
- Updating paper information (links, findings)
- Suggesting improvements to categorization
This documentation is licensed under CC BY-NC 4.0. Individual papers retain their original copyrights.