Security researcher claims they found KVM guest-host escape flaw
Paulos Yibelo claims a KVM guest-to-host root escape zero-day found via Vercel’s Firecracker sandbox bounty.
Security researcher Paulos Yibelo says a Vercel bug-bounty submission uncovered a full guest-to-host root escape in Linux KVM, the hypervisor behind Firecracker MicroVMs. Vercel CEO Guillermo Rauch said the company confirmed a KVM zero-day affecting its Sandbox product, which runs AI-agent workloads in Firecracker. No CVE, patch, proof-of-concept, or mailing-list discussion is public, and exploitation has not been reported. KVM also underpins clouds and platforms from AWS, Google, Nutanix, HPE, and Proxmox; The Register notes Januscape as another serious KVM bug found this year.
- Paulos Yibelo reported a full KVM guest-to-host root escape via Vercel’s bounty.
- Vercel CEO Guillermo Rauch said the company confirmed a KVM zero-day.
- Vercel Sandbox uses AWS-originated Firecracker MicroVMs, which rely on Linux KVM.
- AWS, Google, Nutanix, HPE, and Proxmox also use KVM; no CVE or patch details are public.
- The Register notes Januscape as an earlier KVM bug this year.
Full article405 words · extracted from theregister.com · click to collapse
offbeat
Firecracker MicroVMs, which started at AWS, seem to be the problem
Linux KVM, the hypervisor favoured by hyperscale clouds, apparently has a full VM escape bug.
That nasty news came from security researcher Paulos Yibelo, who on X shared a screenshot of a bug bounty award he won for discovering what he described as “Full VM escape zeroday (guest>host root in industry standard hypervisors)!”
The bug bounty Yibelo participated in is run by Vercel, a company that provides MicroVMs as sandboxes for AI agents to work inside. The company’s Sandbox uses Firecracker MicroVMs, a technology created by AWS, which relies on Linux KVM – the kernel level hypervisor in Linux.
REG AD
Vercel CEO Guillermo Rauch named KVM as the hypervisor identified by Yibelo.
REG AD
“We’ve confirmed a KVM 0day through our Vercel Sandbox bounty program. Affecting the industry’s gold standard solution for Linux virtualization,” he wrote.
And that’s all the info that has made it into the public view at this time. The Register can find no chat on relevant mailing lists. We have asked Rauch and Yibelo for additional details.
Hopefully, we don’t hear from either of them for days or weeks, for two reasons.
One is that guest-host escapes are the nightmare virtualization scenario because they mean whoever runs a guest VM could take over an entire server, and perhaps gain the ability to control other guests.
The other is that KVM is astoundingly prevalent: AWS and Google both use it to power their public clouds. Enterprise virtualization players Nutanix, HPE, and Proxmox also rely on KVM. And of course KVM is also in Firecracker, which is open source and could therefore be running in all sorts of places.
Whatever Yibelo discovered therefore very much needs a responsible disclosure process, because if hints about the flaw emerge it could allow attackers to do a lot of damage.
Once a fix is found, the next question is whether implementing it will require disruption or downtime. It’s possible to hot-patch KVM, and to migrate live VMs from vulnerable hosts to machines running a patched version of Linux. Hopefully those techniques will work.
This might be the second nasty bug discovered in KVM this year, after the so-called Januscape flaw.
REG AD
Beyond the potential risks this bug created, observers have suggested the potential seriousness of the flaw means Yibelo’s reward should exceed the $50,000 available under Vercel’s bug bounty program. ®