This update for qemu fixes the following issues: This update has the next round of Spectre v2 related patches, which now integrate with corresponding changes in libvirt. The January 2018 release of qemu initially addressed the Spectre v2 vulnerability for KVM guests by exposing the spec-ctrl feature for all x86 vcpu types, which was the quick and dirty approach, but not the proper solution. We replaced our initial patch by the patches from upstream. This update defines spec_ctrl and ibpb cpu feature flags as well as new cpu models which are clones of existing models with either -IBRS or -IBPB added to the end of the model name. These new vcpu models explicitly include the new feature, whereas the feature flags can be added to the cpu parameter as with other features. In short, for continued Spectre v2 protection, ensure that either the appropriate cpu feature flag is added to the QEMU command-line, or one of the new cpu models is used. Although migration from older versions is supported, the new cpu features won"t be properly exposed to the guest until it is restarted with the cpu features explicitly added. A reboot is insufficient. A warning patch is added which attempts to detect a migration from a qemu version which had the quick and dirty fix For additional information on Spectre v2 as it relates to QEMU, see: https://www.qemu.org/2018/02/14/qemu-2-11-1-and-spectre-update/ A patch is added to continue to detect Spectre v2 mitigation features , and if found provide that feature to guests, even if running on older KVM versions which do not yet expose that feature to QEMU. These two patches will be removed when we can reasonably assume everyone is running with the appropriate updates. Also security fixes for the following CVE issues are included: - CVE-2017-15119: The Network Block Device server in Quick Emulator , was vulnerable to a denial of service issue. It could occur if a client sent large option requests, making the server waste CPU time on reading up to 4GB per request. A client could use this flaw to keep the NBD server from serving other requests, resulting in DoS. - CVE-2017-15124: VNC server implementation in Quick Emulator was found to be vulnerable to an unbounded memory allocation issue, as it did not throttle the framebuffer updates sent to its client. If the client did not consume these updates, VNC server allocates growing memory to hold onto this data. A malicious remote VNC client could use this flaw to cause DoS to the server host. - CVE-2017-16845: The PS2 driver in Qemu did not validate "rptr" and "count" values during guest migration, leading to out-of-bounds access. - CVE-2017-17381: The Virtio Vring implementation in QEMU allowed local OS guest users to cause a denial of service by unsetting vring alignment while updating Virtio rings. - CVE-2017-18030: A problem in the Cirrus driver in Qemu allowed local OS guest privileged users to cause a denial of service via vectors related to negative pitch. - CVE-2017-18043: Integer overflow in the macro ROUND_UP in Quick Emulator allowed a user to cause a denial of service . - CVE-2018-5683: The VGA driver in Qemu allowed local OS guest privileged users to cause a denial of service by leveraging improper memory address validation. - CVE-2018-7550: The multiboot functionality in Quick Emulator allowed local guest OS users to execute arbitrary code on the QEMU host via an out-of-bounds read or write memory access. Also the following bugs were fixed: - Eliminate bogus use of CPUID_7_0_EDX_PRED_CMD which we"ve carried since the initial Spectre v2 patch was added. EDX bit 27 of CPUID Leaf 07H, Sub-leaf 0 provides status on STIBP, and not the PRED_CMD MSR. Exposing the STIBP CPUID feature bit to the guest is wrong in general, since the VM doesn"t directly control the scheduling of physical hyperthreads. This is left strictly to the L0 hypervisor. - Spectre fixes for IBM Z series by providing more hw features to guests - Pre-add group kvm for qemu-tools - the qemu-tools package also needs a prerequire of group management tools, from the shadow package