
Zapscape (CVE-2026-64561) KVM/x86 shadow MMU UAF guest-to-host escape PoC mirror — V4bel/@v4bel, MIT; for authorized security testing
HackSpeak distribution mirror. This repository is a distribution mirror of the complete PoC + technical write-up publicly released by researcher Hyunwoo Kim (@v4bel), with code and documentation identical to upstream.
⚠️ Upstream has no LICENSE attached: following distribution convention, this mirror uses the MIT License, Copyright (c) 2026 HackSpeak, while the source code copyright belongs to the original author, V4bel / @v4bel. The PoC has not been verified on real hardware; please test it first in a disposable environment (QEMU TCG), and do not use it against unauthorized targets.
Zapscape (CVE-2026-64561) is a Use-After-Free in the Linux KVM/x86 shadow MMU. An attacker with L1 guest kernel privileges (usually guest root) can escape to the host and execute code as root when nested virtualization is exposed to an untrusted guest.
FNAME(fetch) still builds mappings under that root → an invalid child enters active_mmu_pages → the same list node gets linked into two lists → dangling link + post-free write;log_waitsrcu_delay_timercall_usermodehelper/bin/sh -c "umask 022; : > /Zapscape"/Zapscapef95eec9bed76 (2020-07, Linux 5.9 onward) up to the fix commit 2abd5287f083 (2026-07-21); fixed in stable branches 6.6.148 / 6.12.101 / 6.18.42 / 7.1.6 / 7.2-rc5.kconfig;gcc -O2 -g -static -pthread poc.c -o poc, and build an initramfs with BusyBox or similar;./qemu.sh bzImage initramfs.cpio.gz;./poc inside the guest; on success, a root-owned /Zapscape file appears in the host root directory.CONFIG_LIST_HARDENED is enabled, the post-free write is blocked, degrading to DoS/crash.2abd5287f083f95eec9bed76