Skip to content
OpenAdvisories
High USN-3261-1 37 CVEs

qemu vulnerabilities

Published Apr 20, 2017 · Updated Feb 10, 2026

Ecosystem: Ubuntu

Summary

Zhenhao Hong discovered that QEMU incorrectly handled the Virtio GPU
device. An attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. This issue only affected Ubuntu
16.04 LTS and Ubuntu 16.10. (CVE-2016-10028, CVE-2016-10029)

Li Qiang discovered that QEMU incorrectly handled the 6300esb watchdog. A
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2016-10155)

Li Qiang discovered that QEMU incorrectly handled the i.MX Fast Ethernet
Controller. A privileged attacker inside the guest could use this issue to
cause QEMU to crash, resulting in a denial of service. This issue only
affected Ubuntu 16.04 LTS and Ubuntu 16.10. (CVE-2016-7907)

It was discovered that QEMU incorrectly handled the JAZZ RC4030 device. A
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2016-8667)

It was discovered that QEMU incorrectly handled the 16550A UART device. A
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2016-8669)

It was discovered that QEMU incorrectly handled the shared rings when used
with Xen. A privileged attacker inside the guest could use this issue to
cause QEMU to crash, resulting in a denial of service, or possibly execute
arbitrary code on the host. (CVE-2016-9381)

Jann Horn discovered that QEMU incorrectly handled VirtFS directory
sharing. A privileged attacker inside the guest could use this issue to
access files on the host file system outside of the shared directory and
possibly escalate their privileges. In the default installation, when QEMU
is used with libvirt, attackers would be isolated by the libvirt AppArmor
profile. (CVE-2016-9602)

Gerd Hoffmann discovered that QEMU incorrectly handled the Cirrus VGA
device when being used with a VNC connection. A privileged attacker inside
the guest could use this issue to cause QEMU to crash, resulting in a
denial of service, or possibly execute arbitrary code on the host. In the
default installation, when QEMU is used with libvirt, attackers would be
isolated by the libvirt AppArmor profile. (CVE-2016-9603)

It was discovered that QEMU incorrectly handled the ColdFire Fast Ethernet
Controller. A privileged attacker inside the guest could use this issue to
cause QEMU to crash, resulting in a denial of service. (CVE-2016-9776)

Li Qiang discovered that QEMU incorrectly handled the Virtio GPU device. An
attacker inside the guest could use this issue to cause QEMU to leak
contents of host memory. This issue only affected Ubuntu 16.04 LTS and
Ubuntu 16.10. (CVE-2016-9845, CVE-2016-9908)

Li Qiang discovered that QEMU incorrectly handled the Virtio GPU device. An
attacker inside the guest could use this issue to cause QEMU to crash,
resulting in a denial of service. This issue only affected Ubuntu 16.04 LTS
and Ubuntu 16.10. (CVE-2016-9846, CVE-2016-9912, CVE-2017-5552,
CVE-2017-5578, CVE-2017-5857)

Li Qiang discovered that QEMU incorrectly handled the USB redirector. An
attacker inside the guest could use this issue to cause QEMU to crash,
resulting in a denial of service. This issue only affected Ubuntu 16.04 LTS
and Ubuntu 16.10. (CVE-2016-9907)

Li Qiang discovered that QEMU incorrectly handled USB EHCI emulation. An
attacker inside the guest could use this issue to cause QEMU to crash,
resulting in a denial of service. (CVE-2016-9911)

Li Qiang discovered that QEMU incorrectly handled VirtFS directory sharing.
A privileged attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service. (CVE-2016-9913, CVE-2016-9914,
CVE-2016-9915, CVE-2016-9916)

Qinghao Tang, Li Qiang, and Jiangxin discovered that QEMU incorrectly
handled the Cirrus VGA device. A privileged attacker inside the guest could
use this issue to cause QEMU to crash, resulting in a denial of service.
(CVE-2016-9921, CVE-2016-9922)

Wjjzhang and Li Qiang discovered that QEMU incorrectly handled the Cirrus
VGA device. A privileged attacker inside the guest could use this issue to
cause QEMU to crash, resulting in a denial of service, or possibly execute
arbitrary code on the host. In the default installation, when QEMU is used
with libvirt, attackers would be isolated by the libvirt AppArmor profile.
(CVE-2017-2615)

It was discovered that QEMU incorrectly handled the Cirrus VGA device. A
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service, or possibly execute arbitrary code
on the host. In the default installation, when QEMU is used with libvirt,
attackers would be isolated by the libvirt AppArmor profile.
(CVE-2017-2620)

It was discovered that QEMU incorrectly handled VNC connections. An
attacker inside the guest could use this issue to cause QEMU to crash,
resulting in a denial of service. (CVE-2017-2633)

Li Qiang discovered that QEMU incorrectly handled the ac97 audio device. A
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2017-5525)

Li Qiang discovered that QEMU incorrectly handled the es1370 audio device.
A privileged attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service. (CVE-2017-5526)

Li Qiang discovered that QEMU incorrectly handled the 16550A UART device. A
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2017-5579)

Jiang Xin discovered that QEMU incorrectly handled SDHCI device emulation.
A privileged attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service, or possibly execute arbitrary
code on the host. In the default installation, when QEMU is used with
libvirt, attackers would be isolated by the libvirt AppArmor profile.
(CVE-2017-5667)

Li Qiang discovered

Fixed packages 2

ReleasePackageFixed in
Ubuntu · 14.04 LTS 14.04:LTS qemu 2.0.0+dfsg-2ubuntu1.33
Ubuntu · 16.04 LTS 16.04:LTS qemu 1:2.5+dfsg-5ubuntu10.11

Vulnerabilities 37

References

  • report
    https://ubuntu.com/security/CVE-2016-7907
  • report
    https://ubuntu.com/security/CVE-2016-8667
  • report
    https://ubuntu.com/security/CVE-2016-8669
  • report
    https://ubuntu.com/security/CVE-2016-9381
  • report
    https://ubuntu.com/security/CVE-2016-9602
  • report
    https://ubuntu.com/security/CVE-2016-9603
  • report
    https://ubuntu.com/security/CVE-2016-9776
  • report
    https://ubuntu.com/security/CVE-2016-9845
  • report
    https://ubuntu.com/security/CVE-2016-9846
  • report
    https://ubuntu.com/security/CVE-2016-9907
  • report
    https://ubuntu.com/security/CVE-2016-9908
  • report
    https://ubuntu.com/security/CVE-2016-9911
  • report
    https://ubuntu.com/security/CVE-2016-9912
  • report
    https://ubuntu.com/security/CVE-2016-9913
  • report
    https://ubuntu.com/security/CVE-2016-9914
  • report
    https://ubuntu.com/security/CVE-2016-9915
  • report
    https://ubuntu.com/security/CVE-2016-9916
  • report
    https://ubuntu.com/security/CVE-2016-9921
  • report
    https://ubuntu.com/security/CVE-2016-9922
  • report
    https://ubuntu.com/security/CVE-2016-10028
  • report
    https://ubuntu.com/security/CVE-2016-10029
  • report
    https://ubuntu.com/security/CVE-2016-10155
  • report
    https://ubuntu.com/security/CVE-2017-2615
  • report
    https://ubuntu.com/security/CVE-2017-2620
  • report
    https://ubuntu.com/security/CVE-2017-2633
  • report
    https://ubuntu.com/security/CVE-2017-5525
  • report
    https://ubuntu.com/security/CVE-2017-5526
  • report
    https://ubuntu.com/security/CVE-2017-5552
  • report
    https://ubuntu.com/security/CVE-2017-5578
  • report
    https://ubuntu.com/security/CVE-2017-5579
  • report
    https://ubuntu.com/security/CVE-2017-5667
  • report
    https://ubuntu.com/security/CVE-2017-5856
  • report
    https://ubuntu.com/security/CVE-2017-5857
  • report
    https://ubuntu.com/security/CVE-2017-5898
  • report
    https://ubuntu.com/security/CVE-2017-5973
  • report
    https://ubuntu.com/security/CVE-2017-5987
  • report
    https://ubuntu.com/security/CVE-2017-6505