Skip to main content
Januscape (CVE-2026-53359) was disclosed through coordinated responsible disclosure. After reporting to security@kernel.org, the vulnerability was patched in mainline Linux before any public information was released. Once the patch landed, the researcher submitted details and a working exploit to linux-distros@vs.openwall.org under a 5-day embargo, giving downstream distribution maintainers time to prepare their own backports. The embargo expired cleanly, and Januscape was published simultaneously on the oss-security mailing list and in this documentation on 2026-07-06 — approximately 24 days after first contact with the kernel security team. The bug was also exploited as a 0-day in Google kvmCTF prior to disclosure. Google kvmCTF is a live-kernel capture-the-flag competition running on production GCP infrastructure, where participants attempt to escape a KVM guest and read a flag from the host. Using Januscape in that context validated the full guest-to-host escape primitive against a real cloud environment, not just an isolated lab setup. An additional historical note: the root-cause commit 2032a93d66fa that introduced the vulnerable kvm_mmu_get_child_sp() logic landed on 2010-08-01, meaning the bug lay dormant for approximately 16 years before being identified and patched on 2026-06-19.

​
Disclosure Steps

​
Researcher

Januscape was discovered and reported by Hyunwoo Kim (@v4bel). To the best of public knowledge, this is the first guest-to-host KVM exploit demonstrated as triggerable on both Intel (VMX) and AMD (SVM) platforms, owing to the shared arch/x86/kvm/mmu/mmu.c code path where the vulnerability lives.

​
Google kvmCTF Context

Januscape was weaponised as a 0-day in Google kvmCTF before the coordinated disclosure began. kvmCTF runs on live GCP infrastructure: participants are allocated a guest VM and must escape to the host to capture a flag. Achieving a guest-to-host escape in kvmCTF against production cloud hardware confirmed that the full exploit primitive is viable in a real multi-tenant environment, not merely a local lab configuration.

​
16-Year Dormancy

The vulnerable logic in kvm_mmu_get_child_sp() — performing the child shadow page reuse check before computing the role, and checking only gfn without checking role — was introduced by commit 2032a93d66fa on 2010-08-01. It was patched by 81ccda30b4e8 on 2026-06-19, giving it a window of approximately 16 years during which any kernel supporting KVM nested virtualisation on x86 was affected.
Key links
How the linux-distros embargo process worksThe linux-distros@vs.openwall.org list is a private, coordinated disclosure channel for Linux distribution security teams (Red Hat, Debian, Ubuntu, SUSE, Arch, and others). When a reporter submits a vulnerability, they agree on an embargo deadline — typically 7 days or fewer for already-patched issues. During the embargo, distribution maintainers receive the full details and a working exploit so they can prepare, test, and stage backport patches. When the embargo expires, all parties publish simultaneously: the reporter posts to oss-security and distributions release advisories. For Januscape, the mainline patch (81ccda30b4e8) had already landed two weeks before the linux-distros submission, so distributions could backport a known-good commit rather than coordinating a patch from scratch.