hn.today

Escaping Firecracker from Guest Userspace

coinspect.com8 points0 comments
Screenshot of Escaping Firecracker from Guest Userspace

Firecracker isolates untrusted workloads in lightweight virtual machines, including environments used for cloud functions and AI agents. Researchers demonstrated an escape from guest userspace: root inside the guest, without control of its kernel, could read and modify live memory in Firecracker’s host-side virtual-machine monitor (VMM), then execute code there. The flaw affected machines restored from snapshots using the File memory backend when a balloon or virtio-mem device discarded guest memory. Under memory pressure, a failed fixed-address replacement could remove the snapshot mapping while leaving its KVM memory slot active. When Firecracker reused that address, the guest’s access still reached the new VMM allocation. The researchers’ exploit triggered this failure with a per-microVM memory limit.

A second weakness, FC-03, let compromised VMM code use host operations blocked by Firecracker’s seccomp policy. In particular, it could create a fresh io_uring ring and use it to send a message to a host loopback listener; related tests also demonstrated filesystem changes. These actions remained subject to the Firecracker process’s credentials and jailer constraints. A separate test combined the chain with Linux CVE-2026-43366 to panic a vulnerable host; host-kernel code execution was not attempted. The memory flaw, CVE-2026-122192, affects Firecracker v0.23.0 through v1.16.1 and is fixed in v1.16.2 and v1.17.0. A seccomp redesign is under review for FC-03. AWS says its services, including Lambda, are unaffected and require no customer action.

Read on coinspect.com0 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.