QEMU guest agent CVE fix and build proposals

QEMU development centered on iterative patches for a guest agent privilege escalation flaw, alongside larger proposals for snapshot loading, vhost-user isolation, and build system changes. The traffic reflects ongoing hardening and multi-target infrastructure work on the qemu-devel list.

Guest agent SSH commands close symlink TOCTOU

Multiple patch revisions on qemu-devel address CVE-2026-12080 in the QEMU guest agent guest-ssh-* commands. The flaw is a symlink race that let unprivileged users trigger root-owned file takeover or chown escalation when handling authorized_keys. Later versions drop effective user and group IDs via setuid/setgid rather than relying solely on symlink checks, so operators running the agent should track the series for the final approach.

Fast snapshot load via userfaultfd

A v4 patch series proposes faster VM snapshot resume in QEMU migration code. It combines userfaultfd for lazy RAM loading with an eager background thread to reduce restore latency. The change matters for environments that checkpoint and restart guests frequently and want lower downtime without full pre-faulting.

vhost-user memory isolation RFC

An RFC series of 15 patches introduces isolated memory for vhost-user devices. It uses bounce buffers and shadow virtqueues so the backend no longer maps guest RAM directly. Readers working on secure device backends or multi-tenant hosts gain a path to stronger isolation boundaries.

TCG tests move to Meson

A 103-patch v6 series converts the QEMU TCG test suite from Makefiles to Meson. The goal is tighter integration with the rest of the build and simpler maintenance. Contributors who extend or run instruction-level tests will see the practical impact once the conversion lands.

Dynamic machine-type filtering for single binary

A 27-patch series replaces static machine-type filtering with a dynamic TYPE_TARGET_SPECIFIC is_available() hook. The work supports multi-target single-binary QEMU builds by deciding availability at runtime. It reduces the need for separate binaries when packaging or deploying across architectures.