Уязвимость VENOM KVM/QEMU CVE-2015-3456

Только скорее не перезагрузить, а выключить и затем включить vds.

Поправил, имелось ввиду жесткая перезагрузка через qemu

Кто-то может достать детектор? Там ссылка только для зарегистрированных.

A security flaw has been found in QEMU's Floppy Disk Controller (FDC) emulation code. It is advised you upgrade your versions of Xen/KVM as soon as possible.

This flaw only affects Xen & KVM virtualizations. No action is required for OpenVZ.

Details

An out-of-bounds memory access flaw was found in the way QEMU's virtual Floppy Disk Controller (FDC) handled FIFO buffer access while processing certain FDC commands. A privileged guest user could use this flaw to crash the guest or, potentially, execute arbitrary code on the host with the privileges of the host's QEMU process corresponding to the guest.

The flaw affects all versions of QEMU going back to 2004, when the virtual floppy controller was first introduced. Fortunately there is no known exploit that can successfully attack the flaw so far. Yet VENOM is risky enough to be considered a high-priority vulnerability. In order to mount an exploit attempt, a user on the guest machine would need sufficient permissions to access the floppy disk controller I/O ports. On Linux guests, that means the user would need to have root access or otherwise elevated privilege. But on Windows guests, practically any user would have sufficient permissions.

Upgrading a KVM Hypervisor

yum update qemu-kvm

Following the update, the guests (virtual machines) need to be powered off and started up again for the update to take effect. Please note that it is not enough to restart the guests because a restarted guest would continue running using the same (old, not updated) QEMU binary.

Upgrading a Xen Hypervisor (RHEL 6)

yum update xen

Following the update, the guests (virtual machines) need to be powered off and started up again for the update to take effect. Please note that it is not enough to restart the guests because a restarted guest would continue running using the same (old, not updated) QEMU binary.

Upgrading a Xen Hypervisor (RHEL 5)

If your hypervisor is RHEL 5 and you use the 3.4.x version of Xen please see the following document https://documentation.solusvm.com/display/DOCS/Xen+3.4.x+RPM+Releases

References

http://www.theregister.co.uk/2015/05/13/heartbleed_eat_your_heart_out_venom_vuln_poisons_countless_vms

http://venom.crowdstrike.com

Вроде как нет смысла переживать, если у вас по дефолту в настройках виртуализации был отключена эмуляция Floppy...

Проблема проявляется во всех гостевых системах на базе архитектуры x86 и x86-64, выполняемых с использованием гипервизора Xen в режиме полной виртуализации (HVM) и в системах на базе QEMU/KVM. Тип эмулируемого оборудования и настройки запуска QEMU не имеют значения, так как в режимах PIIX и ICH9 создаётся мост для шины ISA, в котором в любом случае доступен виртуальный контроллер флоппи-дисков. Также не имеет значение наличие в гостевой системе файла устройства для доступа к флоппи-диску, так как эксплуатация производится через обращение к портам ввода/вывода.

В proxmox уже заткнули