A public report says a guest disk copy can smash host heap
Brief
A default single-disk PC is not the setup the report describes.
Notes
qemu-project/qemu#4173. Public. Kind::Security, Device NVME, Workflow::Needs Info. Assignees: Klaus Jensen, Stefan Hajnoczi. No CVE label. It is still open.
The public text describes a bounce buffer versus a destination metadata window sized with inconsistent namespace geometry. It claims a host heap out-of-bounds write, and that this can become QEMU-process code execution. That is the issue’s claim, not a confirmation.
The report says a default PC with one disk that has no integrity metadata does not trigger. The test was run with TCG. The named path is the NVMe device emulator, which is shared with KVM, so this is not treated as TCG-only. No landed commit. A July NVMe copy series resolves other issue numbers, not #4173. That series is not the fix. First and last affected release are unconfirmed. The report names v11.1.0-rc3 as tested.
Commit gitlab qemu work_items/4173