USN-3261-1: QEMU vulnerabilities<\/p>\n
20th April, 2017<\/em><\/p>\n A security issue affects these releases of Ubuntu and its Several security issues were fixed in QEMU.\n<\/p>\n Zhenhao Hong discovered that QEMU incorrectly handled the Virtio GPU Li Qiang discovered that QEMU incorrectly handled the 6300esb watchdog. A Li Qiang discovered that QEMU incorrectly handled the i.MX Fast Ethernet It was discovered that QEMU incorrectly handled the JAZZ RC4030 device. A It was discovered that QEMU incorrectly handled the 16550A UART device. A It was discovered that QEMU incorrectly handled the shared rings when used Jann Horn discovered that QEMU incorrectly handled VirtFS directory Gerd Hoffmann discovered that QEMU incorrectly handled the Cirrus VGA It was discovered that QEMU incorrectly handled the ColdFire Fast Ethernet Li Qiang discovered that QEMU incorrectly handled the Virtio GPU device. An Li Qiang discovered that QEMU incorrectly handled the Virtio GPU device. An Li Qiang discovered that QEMU incorrectly handled the USB redirector. An Li Qiang discovered that QEMU incorrectly handled USB EHCI emulation. An Li Qiang discovered that QEMU incorrectly handled VirtFS directory sharing. Qinghao Tang, Li Qiang, and Jiangxin discovered that QEMU incorrectly Wjjzhang and Li Qiang discovered that QEMU incorrectly handled the Cirrus It was discovered that QEMU incorrectly handled the Cirrus VGA device. A It was discovered that QEMU incorrectly handled VNC connections. An Li Qiang discovered that QEMU incorrectly handled the ac97 audio device. A Li Qiang discovered that QEMU incorrectly handled the es1370 audio device. Li Qiang discovered that QEMU incorrectly handled the 16550A UART device. A Jiang Xin discovered that QEMU incorrectly handled SDHCI device emulation. Li Qiang discovered that QEMU incorrectly handled the MegaRAID SAS device. Li Qiang discovered that QEMU incorrectly handled the CCID Card device. A Li Qiang discovered that QEMU incorrectly handled USB xHCI controller Jiang Xin and Wjjzhang discovered that QEMU incorrectly handled SDHCI Li Qiang discovered that QEMU incorrectly handled USB OHCI controller The problem can be corrected by updating your system to the following To update your system, please follow these instructions: After a standard system update you need to restart all QEMU virtual CVE-2016-10028<\/a>, <\/p>\n CVE-2016-10029<\/a>, <\/p>\n CVE-2016-10155<\/a>, <\/p>\n CVE-2016-7907<\/a>, <\/p>\n CVE-2016-8667<\/a>, <\/p>\n CVE-2016-8669<\/a>, <\/p>\n CVE-2016-9381<\/a>, <\/p>\n CVE-2016-9602<\/a>, <\/p>\n CVE-2016-9603<\/a>, <\/p>\n CVE-2016-9776<\/a>, <\/p>\n CVE-2016-9845<\/a>, <\/p>\n CVE-2016-9846<\/a>, <\/p>\n CVE-2016-9907<\/a>, <\/p>\n CVE-2016-9908<\/a>, <\/p>\n CVE-2016-9911<\/a>, <\/p>\n CVE-2016-9912<\/a>, <\/p>\n CVE-2016-9913<\/a>, <\/p>\n CVE-2016-9914<\/a>, <\/p>\n CVE-2016-9915<\/a>, <\/p>\n CVE-2016-9916<\/a>, <\/p>\n CVE-2016-9921<\/a>, <\/p>\n CVE-2016-9922<\/a>, <\/p>\n CVE-2017-2615<\/a>, <\/p>\n CVE-2017-2620<\/a>, <\/p>\n CVE-2017-2633<\/a>, <\/p>\n CVE-2017-5525<\/a>, <\/p>\n CVE-2017-5526<\/a>, <\/p>\n CVE-2017-5552<\/a>, <\/p>\n CVE-2017-5578<\/a>, <\/p>\n CVE-2017-5579<\/a>, <\/p>\n CVE-2017-5667<\/a>, <\/p>\n CVE-2017-5856<\/a>, <\/p>\n CVE-2017-5857<\/a>, <\/p>\n CVE-2017-5898<\/a>, <\/p>\n CVE-2017-5973<\/a>, <\/p>\n CVE-2017-5987<\/a>, <\/p>\n CVE-2017-6505<\/a><\/p>\n Source: USN-3261-1: QEMU vulnerabilities<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" USN-3261-1: QEMU vulnerabilities Ubuntu Security Notice USN-3261-1 20th April, 2017 qemu vulnerabilities A security issue affects these releases of Ubuntu and its derivatives: Ubuntu 16.10 Ubuntu 16.04 LTS Ubuntu 14.04 LTS Summary Several security issues were fixed in QEMU. Software description qemu – Machine emulator and virtualizer Details Zhenhao Hong discovered that QEMU incorrectly handled the Virtio GPUdevice. An attacker inside the guest could use this issue to cause QEMU tocrash, resulting in a denial of service. This issue only affected Ubuntu16.04 LTS and Ubuntu 16.10. (CVE-2016-10028, CVE-2016-10029) Li Qiang discovered that QEMU incorrectly handled the 6300esb watchdog. Aprivileged attacker inside the guest could use this issue to cause QEMU tocrash, resulting in a denial of service. (CVE-2016-10155) Li Qiang discovered that QEMU incorrectly handled the i.MX Fast EthernetController. A privileged attacker inside the guest could use this issue tocause [ more… ]<\/a><\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[586],"tags":[587],"class_list":["post-15673","post","type-post","status-publish","format-standard","hentry","category-ubuntu-usn","tag-ubuntu-usn"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/15673","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/comments?post=15673"}],"version-history":[{"count":1,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/15673\/revisions"}],"predecessor-version":[{"id":15674,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/posts\/15673\/revisions\/15674"}],"wp:attachment":[{"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/media?parent=15673"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/categories?post=15673"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jirak.net\/wp\/wp-json\/wp\/v2\/tags?post=15673"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}qemu vulnerabilities<\/h3>\n
\n derivatives:<\/p>\n\n
Summary<\/h3>\n
Software description<\/h3>\n
\n
\n – Machine emulator and virtualizer<\/p>\n<\/li>\n<\/ul>\nDetails<\/h3>\n
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<\/a>, CVE-2016-10029<\/a>)<\/p>\n
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2016-10155<\/a>)<\/p>\n
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<\/a>)<\/p>\n
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2016-8667<\/a>)<\/p>\n
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2016-8669<\/a>)<\/p>\n
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<\/a>)<\/p>\n
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<\/a>)<\/p>\n
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<\/a>)<\/p>\n
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<\/a>)<\/p>\n
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<\/a>, CVE-2016-9908<\/a>)<\/p>\n
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<\/a>, CVE-2016-9912<\/a>, CVE-2017-5552<\/a>,
CVE-2017-5578<\/a>, CVE-2017-5857<\/a>)<\/p>\n
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<\/a>)<\/p>\n
attacker inside the guest could use this issue to cause QEMU to crash,
resulting in a denial of service. (CVE-2016-9911<\/a>)<\/p>\n
A privileged attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service. (CVE-2016-9913<\/a>, CVE-2016-9914<\/a>,
CVE-2016-9915<\/a>, CVE-2016-9916<\/a>)<\/p>\n
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<\/a>, CVE-2016-9922<\/a>)<\/p>\n
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<\/a>)<\/p>\n
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<\/a>)<\/p>\n
attacker inside the guest could use this issue to cause QEMU to crash,
resulting in a denial of service. (CVE-2017-2633<\/a>)<\/p>\n
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2017-5525<\/a>)<\/p>\n
A privileged attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service. (CVE-2017-5526<\/a>)<\/p>\n
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2017-5579<\/a>)<\/p>\n
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<\/a>)<\/p>\n
A privileged attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service. (CVE-2017-5856<\/a>)<\/p>\n
privileged attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. (CVE-2017-5898<\/a>)<\/p>\n
emulation. A privileged attacker inside the guest could use this issue to
cause QEMU to crash, resulting in a denial of service. (CVE-2017-5973<\/a>)<\/p>\n
device emulation. A privileged attacker inside the guest could use this
issue to cause QEMU to crash, resulting in a denial of service.
(CVE-2017-5987<\/a>)<\/p>\n
emulation. A privileged attacker inside the guest could use this issue to
cause QEMU to hang, resulting in a denial of service. (CVE-2017-6505<\/a>)<\/p>\nUpdate instructions<\/h3>\n
\npackage version:<\/p>\n\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.6.1+dfsg-0ubuntu5.4<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 1:2.5+dfsg-5ubuntu10.11<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n
\n
\n 2.0.0+dfsg-2ubuntu1.33<\/a>
\n <\/span>\n <\/dd>\n<\/dl>\n
\nhttps:\/\/wiki.ubuntu.com\/Security\/Upgrades<\/a>.\n<\/p>\n
machines to make all the necessary changes.<\/p>\nReferences<\/h3>\n