File _patchinfo of Package patchinfo.6838

Overview Repositories Revisions Requests Users Attributes Meta

File _patchinfo of Package patchinfo.6838

<patchinfo incident="6838">
  <issue id="1085598" tracker="bnc">[Build 20180315-3] openQA test fails in await_install - qemu-tools installation failed</issue>
  <issue id="1073489" tracker="bnc">VUL-0: CVE-2017-15124 kvm,qemu: Memory exhaustion through framebuffer update request message in VNC server</issue>
  <issue id="1076179" tracker="bnc">VUL-1: CVE-2017-18030: kvm,qemu: Out-of-bounds access in cirrus_invalidate_region routine</issue>
  <issue id="1082276" tracker="bnc">KVM doesn't correctly return CPUID_7_0_EDX_SPEC_CTRL as supported feature</issue>
  <issue id="1076775" tracker="bnc">VUL-1: CVE-2017-18043: kvm,qemu: integer overflow in ROUND_UP macro could result in DoS</issue>
  <issue id="1070144" tracker="bnc">VUL-1: CVE-2017-15119: qemu: DoS via large option request</issue>
  <issue id="1076114" tracker="bnc">VUL-1: CVE-2018-5683: qemu:  Qemu: Out-of-bounds read in vga_draw_text routine</issue>
  <issue id="1040202" tracker="bnc">packages qemu-tools and qemu-ksm: installation error</issue>
  <issue id="1083291" tracker="bnc">VUL-0: CVE-2018-7550 qemu, kvm: i386:  multiboot OOB access while loading kernel image</issue>
  <issue id="1076814" tracker="bnc">[CVE] Spectre qemu fixes for s390x for SLES12 SP2</issue>
  <issue id="1068613" tracker="bnc">VUL-1: CVE-2017-16845: qemu: ps2: information leakage via post_load routine</issue>
  <issue id="1071228" tracker="bnc">VUL-1: CVE-2017-17381: qemu: virtio: divide by zero exception while updating rings</issue>
  <issue id="1068032" tracker="bnc">VUL-0: speculative side channel attacks on various CPU platforms aka "SpectreAttack" and "MeltdownAttack"</issue>
  <issue id="2018-5683" tracker="cve" />
  <issue id="2017-5715" tracker="cve" />
  <issue id="2017-16845" tracker="cve" />
  <issue id="2017-18030" tracker="cve" />
  <issue id="2018-7550" tracker="cve" />
  <issue id="2017-17381" tracker="cve" />
  <issue id="2017-18043" tracker="cve" />
  <issue id="2017-15124" tracker="cve" />
  <issue id="2017-15119" tracker="cve" />
  <category>security</category>
  <rating>important</rating>
  <packager>bfrogers</packager>
  <description>
  
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. (CVE-2017-5715
bsc#1068032)

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(s), 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 (it only
detects certain cases, but hopefully is helpful.)
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 (as shown by cpuid), and if found provide that feature
to guests, even if running on older KVM (kernel) versions which
do not yet expose that feature to QEMU. (bsc#1082276)

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 (NBD) server in Quick Emulator (QEMU), 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. (bsc#1070144)
- CVE-2017-15124: VNC server implementation in Quick Emulator (QEMU) 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. (bsc#1073489)
- CVE-2017-16845: The PS2 driver in Qemu did not validate 'rptr' and 'count' values during guest migration, leading to out-of-bounds access. (bsc#1068613)
- CVE-2017-17381: The Virtio Vring implementation in QEMU allowed local OS guest users to cause a denial of service (divide-by-zero error and QEMU process crash) by unsetting vring alignment while updating Virtio rings. (bsc#1071228)
- CVE-2017-18030: A problem in the Cirrus driver in Qemu allowed local OS guest privileged users to cause a denial of service (out-of-bounds array access and QEMU process crash) via vectors related to negative pitch. (bsc#1076179)
- CVE-2017-18043: Integer overflow in the macro ROUND_UP (n, d) in Quick Emulator (Qemu) allowed a user to cause a denial of service (Qemu process crash). (bsc#1076775)
- CVE-2018-5683: The VGA driver in Qemu allowed local OS guest privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) by leveraging improper memory address validation. (bsc#1076114)
- CVE-2018-7550: The multiboot functionality in Quick Emulator (aka QEMU) allowed local guest OS users to execute arbitrary code on the QEMU host via an out-of-bounds read or write memory access. (bsc#1083291)

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
  (bsc#1076814)
- Pre-add group kvm for qemu-tools (bsc#1040202)
- the qemu-tools package also needs a prerequire of group management
  tools, from the shadow package. (bsc#1085598)

</description>
  <summary>Security update for qemu</summary>
</patchinfo>

Places

File _patchinfo of Package patchinfo.6838

Places