3 ms·
Note that the author didn't use any QEMU guest-to-host vulnerability here. The agent found a logic bug that facilitated going straight for the hypervisor from i
by bonzini 2mo ago
Note that the author didn't use any QEMU guest-to-host vulnerability here. The agent found a logic bug that facilitated going straight for the hypervisor from inside the guest, but it isn't caused by the use a memory-unsafe language.
Here is the fix: https://lore.kernel.org/qemu-devel/20260826181552.848617-3-pbonzini@redhat.com/ https://lore.kernel.org/qemu-devel/20260826181552.848617-3-p...
- justincormack 2mo agoAh thats an interesting one.
- bonzini 2mo agoAnd an old one. It's only needed for Windows XP/2003 and honestly it should be retired.