Januscape - The KVM vulnerability that slept for 16 years in the cloud

For 16 years, a massive vulnerability has been sleeping right at the heart of everything that handles virtualization on Linux, and nobody noticed - until Hyunwoo Kim, a security researcher known as @v4bel, showed up. He just uncovered a use-after-free in KVM's shadow MMU, that chunk of code KVM shares between Intel and AMD processors. He named his find Januscape (CVE-2026-53359), and trust me, the scenario is enough to give any hosting provider cold sweats...

In practice, when you rent a VM in the cloud, you're root inside it (fair enough, it's your instance). But if the host allows nested virtualization, well, this flaw swings the door wide open to the physical machine. The proof-of-concept code Kim published simply crashes the host, and he's keeping a second exploit in his back pocket - not publicly disclosed - that turns the same bug into root code execution on the host. And he didn't stumble upon all this by accident: he was taking part in Google's kvmCTF , a program that pays up to $250,000 for a full VM-to-host escape...

At that point, the isolation supposed to separate tenants on the same server falls apart entirely - including the VMs belonging to your neighbors on the same box.

The faulty code has been around since August 2010, back in kernel 2.6.36, and Kim presents Januscape as the first VM-to-host escape that works equally well on both Intel and AMD - to his knowledge, at least.

Now, before you pull the plug on your router and go raise goats in the middle of nowhere, a couple of nuances: the attack requires two conditions to be met - being root inside the guest VM, and the host exposing nested virtualization. Quite a few hosting providers don't enable it, so this isn't exactly a universal apocalypse. That said, for those who do enable it, it's game over.

Good news though: the fix is already out, so if you manage KVM servers, update now. And if you can't patch right away, the workaround is to disable nested virtualization in the meantime, using kvm_intel.nested=0 on Intel or kvm_amd.nested=0 on AMD.

VENOM [FR] was already escaping VMs back in 2015 via an old floppy disk driver, and more recently a kernel flaw hidden for nine years handed out root access on Linux machines. These "ghosts" lie dormant in the kernel for a long time, and they always pick the worst possible moment to wake up. Like other critical Linux flaws that need urgent patching , this one deserves your immediate attention.

Then join my community on Patreon for exclusive articles, advanced tutorials and lots of other surprises I keep for my supporters. It's thanks to you that I can keep sharing my passion after 20 years!