{"id":"CVE-2017-11334","aliases":["DEBIAN-CVE-2017-11334","DSA-3925-1","EUVD-2017-2968","GHSA-4j6c-x59q-c2c4","RHSA-2017:3369","RHSA-2017:3466","RHSA-2017:3470","RHSA-2017:3471","RHSA-2017:3472","RHSA-2017:3473","RHSA-2017:3474","SUSE-SU-2017:2319-1","SUSE-SU-2017:2339-1","SUSE-SU-2017:2416-1","SUSE-SU-2017:2450-1","SUSE-SU-2017:2541-1","SUSE-SU-2017:2936-1","SUSE-SU-2017:2946-1","SUSE-SU-2017:2963-1","SUSE-SU-2017:2969-1","SUSE-SU-2017:3084-1","SUSE-SU-2018:0678-1","UBUNTU-CVE-2017-11334","USN-3575-1","openSUSE-SU-2024:11287-1"],"status":"published","title":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local...","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","severity":{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.00502,"percentile":0.43242,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-125"],"published":"2017-08-02T00:00:00Z","modified":"2026-10-24T10:30:40Z","fixes":[{"ecosystem":"Debian:12","package":"qemu","fixed_in":["1:2.8+dfsg-7"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"qemu","fixed_in":["1:2.8+dfsg-7"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"qemu","fixed_in":["1:2.8+dfsg-7"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.8+dfsg-7"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.8+dfsg-7"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.8+dfsg-7"}]}]},{"source":"osv","ecosystem":"Debian:9","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.8+dfsg-6+deb9u2"}]}],"versions":["1:2.8+dfsg-6","1:2.8+dfsg-6+deb9u1"],"bundled":4},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:openstack:11::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:11::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:11::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:11::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:11::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:9::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:9::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:9::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:9::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:9::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:8::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:8::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:8::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:8::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:8::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:7::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:7::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:7::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:7::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:7::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:6::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:6::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:6::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:6::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:6::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.9.0-16.el7_4.11"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 6","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.5_14-22.25.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.5_14-22.25.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP1-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.5_14-22.25.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Point of Sale 11 SP3","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.5_21-45.5.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP3-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.5_21-45.5.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.0-6.3.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.0-6.3.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.0-6.3.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_22-61.9.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_22-61.9.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_22-61.9.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_22-22.51.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_22-22.51.2"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.22.2"}]}],"bundled":12},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.22.2"}]}],"bundled":12},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.22.2"}]}],"bundled":12},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.22.2"}]}],"bundled":12},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 6","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-33.3.3"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-33.3.3"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP1-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-33.3.3"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-60.3.1"}]}],"bundled":23},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-60.3.1"}]}],"bundled":23},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.2-48.34.3"}]}],"bundled":29},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Point of Sale 11 SP3","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-53.11.1"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP3-LTSS","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-53.11.1"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP3-TERADATA","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-53.11.1"}]}],"bundled":33},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Point of Sale 11 SP3","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.5_21-45.19.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP3-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.5_21-45.19.1"}]}],"bundled":14},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1.5.0+dfsg-3ubuntu5","1.5.0+dfsg-3ubuntu6","1.6.0+dfsg-2ubuntu1","1.6.0+dfsg-2ubuntu2","1.6.0+dfsg-2ubuntu3","1.6.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu1","1.7.0+dfsg-2ubuntu2","1.7.0+dfsg-2ubuntu3","1.7.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu5","1.7.0+dfsg-2ubuntu7","1.7.0+dfsg-2ubuntu8","1.7.0+dfsg-2ubuntu9","1.7.0+dfsg-3ubuntu1~ppa1","1.7.0+dfsg-3ubuntu1","1.7.0+dfsg-3ubuntu2","1.7.0+dfsg-3ubuntu3","1.7.0+dfsg-3ubuntu4","1.7.0+dfsg-3ubuntu5","1.7.0+dfsg-3ubuntu6","1.7.0+dfsg-3ubuntu7","2.0.0~rc1+dfsg-0ubuntu1","2.0.0~rc1+dfsg-0ubuntu2","2.0.0~rc1+dfsg-0ubuntu3","2.0.0~rc1+dfsg-0ubuntu3.1","2.0.0+dfsg-2ubuntu1","2.0.0+dfsg-2ubuntu1.1","2.0.0+dfsg-2ubuntu1.2","2.0.0+dfsg-2ubuntu1.3","2.0.0+dfsg-2ubuntu1.5","2.0.0+dfsg-2ubuntu1.6","2.0.0+dfsg-2ubuntu1.7","2.0.0+dfsg-2ubuntu1.8","2.0.0+dfsg-2ubuntu1.9","2.0.0+dfsg-2ubuntu1.10","2.0.0+dfsg-2ubuntu1.11","2.0.0+dfsg-2ubuntu1.13","2.0.0+dfsg-2ubuntu1.14","2.0.0+dfsg-2ubuntu1.15","2.0.0+dfsg-2ubuntu1.16","2.0.0+dfsg-2ubuntu1.17","2.0.0+dfsg-2ubuntu1.18","2.0.0+dfsg-2ubuntu1.19","2.0.0+dfsg-2ubuntu1.20","2.0.0+dfsg-2ubuntu1.21","2.0.0+dfsg-2ubuntu1.22","2.0.0+dfsg-2ubuntu1.24","2.0.0+dfsg-2ubuntu1.25","2.0.0+dfsg-2ubuntu1.26","2.0.0+dfsg-2ubuntu1.27","2.0.0+dfsg-2ubuntu1.28","2.0.0+dfsg-2ubuntu1.29","2.0.0+dfsg-2ubuntu1.30","2.0.0+dfsg-2ubuntu1.31","2.0.0+dfsg-2ubuntu1.32","2.0.0+dfsg-2ubuntu1.33","2.0.0+dfsg-2ubuntu1.34","2.0.0+dfsg-2ubuntu1.35","2.0.0+dfsg-2ubuntu1.36","2.0.0+dfsg-2ubuntu1.38","2.0.0+dfsg-2ubuntu1.39","2.0.0+dfsg-2ubuntu1.40","2.0.0+dfsg-2ubuntu1.41","2.0.0+dfsg-2ubuntu1.42","2.0.0+dfsg-2ubuntu1.43","2.0.0+dfsg-2ubuntu1.44","2.0.0+dfsg-2ubuntu1.45","2.0.0+dfsg-2ubuntu1.46","2.0.0+dfsg-2ubuntu1.47","2.0.0+dfsg-2ubuntu1.47+esm1","2.0.0+dfsg-2ubuntu1.47+esm2","2.0.0+dfsg-2ubuntu1.47+esm3","2.0.0+dfsg-2ubuntu1.47+esm4","2.0.0+dfsg-2ubuntu1.47+esm6"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["1:2.3+dfsg-5ubuntu9","1:2.3+dfsg-5ubuntu10","1:2.4+dfsg-4ubuntu1","1:2.4+dfsg-4ubuntu2","1:2.4+dfsg-4ubuntu3","1:2.4+dfsg-5ubuntu3","1:2.5+dfsg-1ubuntu2","1:2.5+dfsg-1ubuntu3","1:2.5+dfsg-1ubuntu4","1:2.5+dfsg-1ubuntu5","1:2.5+dfsg-5ubuntu1","1:2.5+dfsg-5ubuntu2","1:2.5+dfsg-5ubuntu4","1:2.5+dfsg-5ubuntu6","1:2.5+dfsg-5ubuntu7","1:2.5+dfsg-5ubuntu10","1:2.5+dfsg-5ubuntu10.1","1:2.5+dfsg-5ubuntu10.2","1:2.5+dfsg-5ubuntu10.3","1:2.5+dfsg-5ubuntu10.4","1:2.5+dfsg-5ubuntu10.5","1:2.5+dfsg-5ubuntu10.6","1:2.5+dfsg-5ubuntu10.7","1:2.5+dfsg-5ubuntu10.8","1:2.5+dfsg-5ubuntu10.9","1:2.5+dfsg-5ubuntu10.10","1:2.5+dfsg-5ubuntu10.11","1:2.5+dfsg-5ubuntu10.13","1:2.5+dfsg-5ubuntu10.14","1:2.5+dfsg-5ubuntu10.15","1:2.5+dfsg-5ubuntu10.16","1:2.5+dfsg-5ubuntu10.20","1:2.5+dfsg-5ubuntu10.21","1:2.5+dfsg-5ubuntu10.22","1:2.5+dfsg-5ubuntu10.24","1:2.5+dfsg-5ubuntu10.25","1:2.5+dfsg-5ubuntu10.26","1:2.5+dfsg-5ubuntu10.28","1:2.5+dfsg-5ubuntu10.29","1:2.5+dfsg-5ubuntu10.30","1:2.5+dfsg-5ubuntu10.31","1:2.5+dfsg-5ubuntu10.32","1:2.5+dfsg-5ubuntu10.33","1:2.5+dfsg-5ubuntu10.34","1:2.5+dfsg-5ubuntu10.35","1:2.5+dfsg-5ubuntu10.36","1:2.5+dfsg-5ubuntu10.37","1:2.5+dfsg-5ubuntu10.38","1:2.5+dfsg-5ubuntu10.39","1:2.5+dfsg-5ubuntu10.40","1:2.5+dfsg-5ubuntu10.41","1:2.5+dfsg-5ubuntu10.42","1:2.5+dfsg-5ubuntu10.43","1:2.5+dfsg-5ubuntu10.44","1:2.5+dfsg-5ubuntu10.45","1:2.5+dfsg-5ubuntu10.46","1:2.5+dfsg-5ubuntu10.47","1:2.5+dfsg-5ubuntu10.48","1:2.5+dfsg-5ubuntu10.49","1:2.5+dfsg-5ubuntu10.51","1:2.5+dfsg-5ubuntu10.51+esm1","1:2.5+dfsg-5ubuntu10.51+esm2","1:2.5+dfsg-5ubuntu10.51+esm3","1:2.5+dfsg-5ubuntu10.51+esm4"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0+dfsg-2ubuntu1.39"}]}],"versions":["1.5.0+dfsg-3ubuntu5","1.5.0+dfsg-3ubuntu6","1.6.0+dfsg-2ubuntu1","1.6.0+dfsg-2ubuntu2","1.6.0+dfsg-2ubuntu3","1.6.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu1","1.7.0+dfsg-2ubuntu2","1.7.0+dfsg-2ubuntu3","1.7.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu5","1.7.0+dfsg-2ubuntu7","1.7.0+dfsg-2ubuntu8","1.7.0+dfsg-2ubuntu9","1.7.0+dfsg-3ubuntu1~ppa1","1.7.0+dfsg-3ubuntu1","1.7.0+dfsg-3ubuntu2","1.7.0+dfsg-3ubuntu3","1.7.0+dfsg-3ubuntu4","1.7.0+dfsg-3ubuntu5","1.7.0+dfsg-3ubuntu6","1.7.0+dfsg-3ubuntu7","2.0.0~rc1+dfsg-0ubuntu1","2.0.0~rc1+dfsg-0ubuntu2","2.0.0~rc1+dfsg-0ubuntu3","2.0.0~rc1+dfsg-0ubuntu3.1","2.0.0+dfsg-2ubuntu1","2.0.0+dfsg-2ubuntu1.1","2.0.0+dfsg-2ubuntu1.2","2.0.0+dfsg-2ubuntu1.3","2.0.0+dfsg-2ubuntu1.5","2.0.0+dfsg-2ubuntu1.6","2.0.0+dfsg-2ubuntu1.7","2.0.0+dfsg-2ubuntu1.8","2.0.0+dfsg-2ubuntu1.9","2.0.0+dfsg-2ubuntu1.10","2.0.0+dfsg-2ubuntu1.11","2.0.0+dfsg-2ubuntu1.13","2.0.0+dfsg-2ubuntu1.14","2.0.0+dfsg-2ubuntu1.15","2.0.0+dfsg-2ubuntu1.16","2.0.0+dfsg-2ubuntu1.17","2.0.0+dfsg-2ubuntu1.18","2.0.0+dfsg-2ubuntu1.19","2.0.0+dfsg-2ubuntu1.20","2.0.0+dfsg-2ubuntu1.21","2.0.0+dfsg-2ubuntu1.22","2.0.0+dfsg-2ubuntu1.24","2.0.0+dfsg-2ubuntu1.25","2.0.0+dfsg-2ubuntu1.26","2.0.0+dfsg-2ubuntu1.27","2.0.0+dfsg-2ubuntu1.28","2.0.0+dfsg-2ubuntu1.29","2.0.0+dfsg-2ubuntu1.30","2.0.0+dfsg-2ubuntu1.31","2.0.0+dfsg-2ubuntu1.32","2.0.0+dfsg-2ubuntu1.33","2.0.0+dfsg-2ubuntu1.34","2.0.0+dfsg-2ubuntu1.35","2.0.0+dfsg-2ubuntu1.36","2.0.0+dfsg-2ubuntu1.38"],"bundled":11},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.5+dfsg-5ubuntu10.22"}]}],"versions":["1:2.3+dfsg-5ubuntu9","1:2.3+dfsg-5ubuntu10","1:2.4+dfsg-4ubuntu1","1:2.4+dfsg-4ubuntu2","1:2.4+dfsg-4ubuntu3","1:2.4+dfsg-5ubuntu3","1:2.5+dfsg-1ubuntu2","1:2.5+dfsg-1ubuntu3","1:2.5+dfsg-1ubuntu4","1:2.5+dfsg-1ubuntu5","1:2.5+dfsg-5ubuntu1","1:2.5+dfsg-5ubuntu2","1:2.5+dfsg-5ubuntu4","1:2.5+dfsg-5ubuntu6","1:2.5+dfsg-5ubuntu7","1:2.5+dfsg-5ubuntu10","1:2.5+dfsg-5ubuntu10.1","1:2.5+dfsg-5ubuntu10.2","1:2.5+dfsg-5ubuntu10.3","1:2.5+dfsg-5ubuntu10.4","1:2.5+dfsg-5ubuntu10.5","1:2.5+dfsg-5ubuntu10.6","1:2.5+dfsg-5ubuntu10.7","1:2.5+dfsg-5ubuntu10.8","1:2.5+dfsg-5ubuntu10.9","1:2.5+dfsg-5ubuntu10.10","1:2.5+dfsg-5ubuntu10.11","1:2.5+dfsg-5ubuntu10.13","1:2.5+dfsg-5ubuntu10.14","1:2.5+dfsg-5ubuntu10.15","1:2.5+dfsg-5ubuntu10.16","1:2.5+dfsg-5ubuntu10.20","1:2.5+dfsg-5ubuntu10.21"],"bundled":11},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.0-32.1"}]}],"bundled":135}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"qemu","product":"qemu"}],"references":[{"url":"https://access.redhat.com/errata/RHSA-2017:3473","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1471638","tags":["x_refsource_CONFIRM","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix","report"]},{"url":"https://access.redhat.com/errata/RHSA-2017:3470","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2017:3472","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory"]},{"url":"http://www.openwall.com/lists/oss-security/2017/07/17/4","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Patch","Third Party Advisory","fix"]},{"url":"https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg03775.html","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Patch","Vendor Advisory","fix","report"]},{"url":"https://access.redhat.com/errata/RHSA-2017:3474","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory"]},{"url":"https://usn.ubuntu.com/3575-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2017:3471","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory"]},{"url":"http://www.securityfocus.com/bid/99895","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2017:3466","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2017:3369","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory"]},{"url":"http://www.debian.org/security/2017/dsa-3925","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","Third Party Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-11334","tags":["advisory"]},{"url":"https://usn.ubuntu.com/3575-1"},{"url":"https://github.com/advisories/GHSA-4j6c-x59q-c2c4"},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-11334","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1489375","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1495474","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1501290","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_3369.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-11334","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-11334","tags":["advisory","report"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-14167","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-14167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-14167","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-15289","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-15289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-15289","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1466190","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1473622","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1498135","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_3466.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-7539","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-7539","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-7539","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-10664","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-10664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-10664","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1498140","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_3470.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1472484","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1498141","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_3471.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_3472.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_3473.json","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1498139","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_3474.json","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172319-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1002573","tags":["report"]},{"url":"https://bugzilla.suse.com/1046637","tags":["report"]},{"url":"https://bugzilla.suse.com/1047675","tags":["report"]},{"url":"https://bugzilla.suse.com/1048920","tags":["report"]},{"url":"https://bugzilla.suse.com/1049578","tags":["report"]},{"url":"https://bugzilla.suse.com/1051787","tags":["report"]},{"url":"https://bugzilla.suse.com/1051788","tags":["report"]},{"url":"https://bugzilla.suse.com/1052686","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12137","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172339-1/","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12855","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172416-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1011144","tags":["report"]},{"url":"https://bugzilla.suse.com/1031692","tags":["report"]},{"url":"https://bugzilla.suse.com/1046636","tags":["report"]},{"url":"https://bugzilla.suse.com/1047674","tags":["report"]},{"url":"https://bugzilla.suse.com/1048296","tags":["report"]},{"url":"https://bugzilla.suse.com/1048902","tags":["report"]},{"url":"https://bugzilla.suse.com/1049381","tags":["report"]},{"url":"https://bugzilla.suse.com/1050268","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172450-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1027519","tags":["report"]},{"url":"https://bugzilla.suse.com/1032598","tags":["report"]},{"url":"https://bugzilla.suse.com/1037413","tags":["report"]},{"url":"https://bugzilla.suse.com/1056278","tags":["report"]},{"url":"https://bugzilla.suse.com/1056281","tags":["report"]},{"url":"https://bugzilla.suse.com/1056282","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14319","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172541-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172936-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1043176","tags":["report"]},{"url":"https://bugzilla.suse.com/1043808","tags":["report"]},{"url":"https://bugzilla.suse.com/1054724","tags":["report"]},{"url":"https://bugzilla.suse.com/1056334","tags":["report"]},{"url":"https://bugzilla.suse.com/1057378","tags":["report"]},{"url":"https://bugzilla.suse.com/1057585","tags":["report"]},{"url":"https://bugzilla.suse.com/1057966","tags":["report"]},{"url":"https://bugzilla.suse.com/1059369","tags":["report"]},{"url":"https://bugzilla.suse.com/1062069","tags":["report"]},{"url":"https://bugzilla.suse.com/1062942","tags":["report"]},{"url":"https://bugzilla.suse.com/1063122","tags":["report"]},{"url":"https://bugzilla.suse.com/997358","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-12809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9524","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172946-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1020427","tags":["report"]},{"url":"https://bugzilla.suse.com/1021741","tags":["report"]},{"url":"https://bugzilla.suse.com/1025109","tags":["report"]},{"url":"https://bugzilla.suse.com/1025311","tags":["report"]},{"url":"https://bugzilla.suse.com/1028184","tags":["report"]},{"url":"https://bugzilla.suse.com/1028656","tags":["report"]},{"url":"https://bugzilla.suse.com/1030624","tags":["report"]},{"url":"https://bugzilla.suse.com/1032075","tags":["report"]},{"url":"https://bugzilla.suse.com/1034866","tags":["report"]},{"url":"https://bugzilla.suse.com/1034908","tags":["report"]},{"url":"https://bugzilla.suse.com/1035406","tags":["report"]},{"url":"https://bugzilla.suse.com/1035950","tags":["report"]},{"url":"https://bugzilla.suse.com/1036211","tags":["report"]},{"url":"https://bugzilla.suse.com/1037242","tags":["report"]},{"url":"https://bugzilla.suse.com/1037334","tags":["report"]},{"url":"https://bugzilla.suse.com/1037336","tags":["report"]},{"url":"https://bugzilla.suse.com/1039495","tags":["report"]},{"url":"https://bugzilla.suse.com/1042159","tags":["report"]},{"url":"https://bugzilla.suse.com/1042800","tags":["report"]},{"url":"https://bugzilla.suse.com/1042801","tags":["report"]},{"url":"https://bugzilla.suse.com/1043073","tags":["report"]},{"url":"https://bugzilla.suse.com/1043296","tags":["report"]},{"url":"https://bugzilla.suse.com/1045035","tags":["report"]},{"url":"https://bugzilla.suse.com/994418","tags":["report"]},{"url":"https://bugzilla.suse.com/994605","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9503","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172963-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1031051","tags":["report"]},{"url":"https://bugzilla.suse.com/1034044","tags":["report"]},{"url":"https://bugzilla.suse.com/1038396","tags":["report"]},{"url":"https://bugzilla.suse.com/1049785","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172969-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1026612","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2633","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20173084-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1013285","tags":["report"]},{"url":"https://bugzilla.suse.com/1014109","tags":["report"]},{"url":"https://bugzilla.suse.com/1014111","tags":["report"]},{"url":"https://bugzilla.suse.com/1014702","tags":["report"]},{"url":"https://bugzilla.suse.com/1015048","tags":["report"]},{"url":"https://bugzilla.suse.com/1016779","tags":["report"]},{"url":"https://bugzilla.suse.com/1021129","tags":["report"]},{"url":"https://bugzilla.suse.com/1023004","tags":["report"]},{"url":"https://bugzilla.suse.com/1023053","tags":["report"]},{"url":"https://bugzilla.suse.com/1023907","tags":["report"]},{"url":"https://bugzilla.suse.com/1024972","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2016-10155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5898","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20180678-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1024307","tags":["report"]},{"url":"https://bugzilla.suse.com/1030144","tags":["report"]},{"url":"https://bugzilla.suse.com/1061081","tags":["report"]},{"url":"https://bugzilla.suse.com/1068032","tags":["report"]},{"url":"https://bugzilla.suse.com/1070158","tags":["report"]},{"url":"https://bugzilla.suse.com/1070159","tags":["report"]},{"url":"https://bugzilla.suse.com/1070160","tags":["report"]},{"url":"https://bugzilla.suse.com/1070163","tags":["report"]},{"url":"https://bugzilla.suse.com/1074562","tags":["report"]},{"url":"https://bugzilla.suse.com/1076116","tags":["report"]},{"url":"https://bugzilla.suse.com/1076180","tags":["report"]},{"url":"https://bugzilla.suse.com/1080635","tags":["report"]},{"url":"https://bugzilla.suse.com/1080662","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-17566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-18030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-5683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7541","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2017-11334","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3575-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3575-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2017-13672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-14167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-15289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-16845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-17381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-18043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-5683","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-8106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-5225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-6855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-8504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-8619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-10028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-1714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-15746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-3639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-03812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-12155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-13164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-6778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-8934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-14364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-1711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-17380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-1983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-27821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-7039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3545","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3682","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2017-11334","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","status":"published","published":"2017-08-02T19:00:00Z","modified":"2024-08-05T18:05:30.599Z","updated_at":"2026-11-02T14:33:19.848632Z"}],"euvd":[{"id":"EUVD-2017-2968","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","status":"published","published":"2017-08-02T19:00:00Z","modified":"2024-08-05T18:05:30Z","updated_at":"2026-11-03T02:23:24.20034Z"}],"ghsa":[{"id":"GHSA-4j6c-x59q-c2c4","title":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local...","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","status":"published","published":"2022-05-13T01:13:42Z","modified":"2025-04-20T03:42:01Z","cvss":[{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T15:01:49.006624Z"}],"nvd":[{"id":"CVE-2017-11334","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","status":"published","published":"2017-08-02T19:29:00.71Z","modified":"2026-06-17T01:01:38.22Z","cvss":[{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"2.0","score":2.1,"vector":"AV:L/AC:L/Au:N/C:N/I:N/A:P","level":"low","assessor":"primary"}],"cwes":["CWE-125"],"updated_at":"2026-11-02T14:03:54.862898Z"}],"osv":[{"id":"CVE-2017-11334","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","status":"published","published":"2017-08-02T19:29:00.71Z","modified":"2026-10-24T10:30:40.701346672Z","cvss":[{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:44:03.851821Z"},{"id":"DEBIAN-CVE-2017-11334","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","status":"published","published":"2017-08-02T19:29:00.71Z","modified":"2026-09-01T20:03:41.034774124Z","cvss":[{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:28.50097Z"},{"id":"RHSA-2017:3369","title":"Red Hat Security Advisory: qemu-kvm-rhev security and bug fix update","status":"published","published":"2024-09-13T13:39:04Z","modified":"2026-06-29T10:18:26Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"RHSA-2017:3466","title":"Red Hat Security Advisory: qemu-kvm-rhev security and bug fix update","status":"published","published":"2024-09-13T13:39:29Z","modified":"2026-07-01T10:03:09Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"RHSA-2017:3470","title":"Red Hat Security Advisory: qemu-kvm-rhev security and bug fix update","status":"published","published":"2024-09-13T13:39:39Z","modified":"2026-07-01T10:03:09Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"RHSA-2017:3471","title":"Red Hat Security Advisory: qemu-kvm-rhev security and bug fix update","status":"published","published":"2024-09-13T13:39:33Z","modified":"2026-07-01T10:03:10Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"RHSA-2017:3472","title":"Red Hat Security Advisory: qemu-kvm-rhev security update","status":"published","published":"2024-09-13T13:39:28Z","modified":"2026-07-01T10:03:10Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"RHSA-2017:3473","title":"Red Hat Security Advisory: qemu-kvm-rhev security update","status":"published","published":"2024-09-13T13:39:19Z","modified":"2026-07-01T10:03:11Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"RHSA-2017:3474","title":"Red Hat Security Advisory: qemu-kvm-rhev security and bug fix update","status":"published","published":"2024-09-13T13:39:24Z","modified":"2026-07-01T10:03:11Z","cvss":[{"version":"3.0","score":5.5,"vector":"CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","level":"medium"}],"updated_at":"2026-11-02T15:53:04.822845Z"},{"id":"UBUNTU-CVE-2017-11334","description":"The address_space_write_continue function in exec.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area.","status":"published","published":"2017-08-02T00:00:00Z","modified":"2026-06-09T21:15:32.148000893Z","cvss":[{"version":"3.1","score":4.4,"vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"},{"version":"3.0","score":4.4,"vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:54:13.729565Z"},{"id":"DSA-3925-1","title":"qemu - security update","status":"published","published":"2017-08-04T00:00:00Z","modified":"2026-03-09T01:19:02.742594Z","updated_at":"2026-11-02T15:46:16.523846Z"},{"id":"openSUSE-SU-2024:11287-1","title":"qemu-6.1.0-32.1 on GA media","description":"These are all security issues fixed in the qemu-6.1.0-32.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2025-05-07T18:08:57.481645Z","updated_at":"2026-11-02T16:58:34.894275Z"},{"id":"SUSE-SU-2017:2319-1","title":"Security update for xen","description":"This update for xen fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-12135: Unbounded recursion in grant table code allowed a malicious\n  guest to crash the host or potentially escalate privileges/leak information\n  (XSA-226, bsc#1051787).\n- CVE-2017-12137: Incorrectly-aligned updates to pagetables allowed for\n  privilege escalation (XSA-227, bsc#1051788).\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest\n  OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP\n  options string (bsc#1049578).\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote\n  attackers to cause a denial of service (daemon crash) by disconnecting during a\n  server-to-client reply attempt (bsc#1046637).\n- CVE-2017-11334: The address_space_write_continue function in exec.c allowed\n  local guest OS privileged users to cause a denial of service (out-of-bounds\n  access and guest instance crash) by leveraging use of qemu_map_ram_ptr to\n  access guest ram block area (bsc#1048920).\n- CVE-2017-10806: Stack-based buffer overflow in hw/usb/redirect.c allowed\n  local guest OS users to cause a denial of service via vectors related to\n  logging debug messages (bsc#1047675).\n- bsc#1052686: Premature clearing of GTF_writing / GTF_reading lead to\n  potentially leaking sensitive information (XSA-230).\n\nThis non-security issue was fixed:\n\n- bsc#1002573: Optimized LVM functions in block-dmmd block-dmmd\n","status":"published","published":"2017-08-31T19:40:38Z","modified":"2026-02-04T03:02:11.015545Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2339-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\n- CVE-2017-12855: Premature clearing of GTF_writing / GTF_reading lead to\n  potentially leaking sensitive information (XSA-230, bsc#1052686).\n- CVE-2017-12135: Unbounded recursion in grant table code allowed a malicious\n  guest to crash the host or potentially escalate privileges/leak information\n  (XSA-226, bsc#1051787).\n- CVE-2017-12137: Incorrectly-aligned updates to pagetables allowed for\n  privilege escalation (XSA-227, bsc#1051788).\n- CVE-2017-11334: The address_space_write_continue function in exec.c allowed\n  local guest OS privileged users to cause a denial of service (out-of-bounds\n  access and guest instance crash) by leveraging use of qemu_map_ram_ptr to\n  access guest ram block area (bsc#1048920).\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest\n  OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP\n  options string (bsc#1049578).\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote\n  attackers to cause a denial of service (daemon crash) by disconnecting during\n  a server-to-client reply attempt (bsc#1046637).\n","status":"published","published":"2017-09-04T11:12:18Z","modified":"2026-02-04T04:09:55.77813Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2416-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n* CVE-2017-10664: Fix DOS vulnerability in qemu-nbd (bsc#1046636)\n* CVE-2017-10806: Fix DOS from stack overflow in debug messages of usb redirection\n  support (bsc#1047674) \n* CVE-2017-11334: Fix OOB access during DMA operation (bsc#1048902) \n* CVE-2017-11434: Fix OOB access parsing dhcp slirp options (bsc#1049381) \n\nFollowing non-security issues were fixed:\n\n- Postrequire acl for setfacl\n- Prerequire shadow for groupadd\n- The recent security fix for CVE-2017-11334 adversely affects Xen.\n  Include two additional patches to make sure Xen is going to be OK.\n- Pre-add group kvm for qemu-tools (bsc#1011144)\n- Fixed a few more inaccuracies in the support docs.\n- Fix support docs to indicate ARM64 is now fully L3 supported in\n  SLES 12 SP3. Apply a few additional clarifications in the support\n  docs. (bsc#1050268)\n- Adjust to libvdeplug-devel package naming changes.\n- Fix migration with xhci (bsc#1048296)\n- Increase VNC delay to fix missing keyboard input events (bsc#1031692)\n- Remove build dependency package iasl used for seabios\n\n","status":"published","published":"2017-09-11T14:31:09Z","modified":"2026-02-04T02:15:57.419931Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2450-1","title":"Security update for xen","description":"This update for xen fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-12135: Unbounded recursion in grant table code allowed a malicious\n  guest to crash the host or potentially escalate privileges/leak information\n  (XSA-226, bsc#1051787).\n- CVE-2017-12137: Incorrectly-aligned updates to pagetables allowed for\n  privilege escalation (XSA-227, bsc#1051788).\n- CVE-2017-11334: The address_space_write_continue function in exec.c allowed\n  local guest OS privileged users to cause a denial of service (out-of-bounds\n  access and guest instance crash) by leveraging use of qemu_map_ram_ptr to\n  access guest ram block area (bsc#1048920).\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest\n  OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP\n  options string (bsc#1049578).\n- CVE-2017-10806: Stack-based buffer overflow in hw/usb/redirect.c allowed\n  local guest OS users to cause a denial of service via vectors related to\n  logging debug messages (bsc#1047675).\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote\n  attackers to cause a denial of service (daemon crash) by disconnecting during\n  a server-to-client reply attempt (bsc#1046637).\n- CVE-2017-12855: Premature clearing of GTF_writing / GTF_reading lead to\n  potentially leaking sensitive information (XSA-230, bsc#1052686).\n- CVE-2017-14316: Missing bound check in function `alloc_heap_pages` for an\n  internal array allowed attackers using crafted hypercalls to execute\n  arbitrary code within Xen (XSA-231, bsc#1056278)\n- CVE-2017-14317: A race in cxenstored may have cause a double-free allowind for\n  DoS of the xenstored daemon (XSA-233, bsc#1056281).\n- CVE-2017-14319: An error while handling grant mappings allowed malicious or\n  buggy x86 PV guest to escalate its privileges or crash the hypervisor (XSA-234,\n  bsc#1056282).\n\nThis non-security issue was fixed:\n\n- bsc#1032598: Prevent removal of NVME devices\n- bsc#1037413: Support for newer intel cpu's, mwait-idle driver and skylake\n","status":"published","published":"2017-09-13T12:41:08Z","modified":"2026-02-04T04:28:29.800144Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2541-1","title":"Security update for xen","description":"This update for xen fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-12135: Unbounded recursion in grant table code allowed a malicious\n  guest to crash the host or potentially escalate privileges/leak information\n  (XSA-226, bsc#1051787).\n- CVE-2017-12137: Incorrectly-aligned updates to pagetables allowed for\n  privilege escalation (XSA-227, bsc#1051788).\n- CVE-2017-11334: The address_space_write_continue function in exec.c allowed\n  local guest OS privileged users to cause a denial of service (out-of-bounds\n  access and guest instance crash) by leveraging use of qemu_map_ram_ptr to\n  access guest ram block area (bsc#1048920).\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest\n  OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP\n  options string (bsc#1049578).\n- CVE-2017-10806: Stack-based buffer overflow in hw/usb/redirect.c allowed\n  local guest OS users to cause a denial of service via vectors related to\n  logging debug messages (bsc#1047675).\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote\n  attackers to cause a denial of service (daemon crash) by disconnecting during \n  a server-to-client reply attempt (bsc#1046637).\n- CVE-2017-12855: Premature clearing of GTF_writing / GTF_reading lead to\n  potentially leaking sensitive information (XSA-230, bsc#1052686).\n- CVE-2017-14316: Missing bound check in function `alloc_heap_pages` for an\n  internal array allowed attackers using crafted hypercalls to execute\n  arbitrary code within Xen (XSA-231, bsc#1056278)\n- CVE-2017-14317: A race in cxenstored may have cause a double-free allowind for\n  DoS of the xenstored daemon (XSA-233, bsc#1056281).\n- CVE-2017-14319: An error while handling grant mappings allowed malicious or\n  buggy x86 PV guest to escalate its privileges or crash the hypervisor (XSA-234,\n  bsc#1056282).\n\nThese non-security issues were fixed:\n\n- bsc#1002573: Optimized LVM functions in block-dmmd block-dmmd\n- bsc#1032598: Prevent removal of NVME devices\n- bsc#1037413: Support for newer intel cpu's, mwait-idle driver and skylake\n","status":"published","published":"2017-09-21T15:30:58Z","modified":"2026-02-04T02:56:21.743107Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2936-1","title":"Security update for qemu","description":"This update for qemu fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-15268: Qemu allowed remote attackers to cause a memory leak by triggering slow data-channel read operations, related to io/channel-websock.c (bsc#1062942).\n- CVE-2017-9524: The qemu-nbd server when built with the Network Block Device (NBD) Server support allowed remote attackers to cause a denial of service (segmentation fault and server crash) by leveraging failure to ensure that all initialization occurs talking to a client in the nbd_negotiate function (bsc#1043808).\n- CVE-2017-15289: The mode4and5 write functions allowed local OS guest privileged users to cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst calculation (bsc#1063122)\n- CVE-2017-15038: Race condition in the v9fs_xattrwalk function local guest OS users to obtain sensitive information from host heap memory via vectors related to reading extended attributes (bsc#1062069)\n- CVE-2017-10911: The make_response function in the Linux kernel allowed guest OS users to obtain sensitive information from host OS (or other guest OS) kernel memory by leveraging the copying of uninitialized padding fields in Xen block-interface response structures (bsc#1057378)\n- CVE-2017-12809: The IDE disk and CD/DVD-ROM Emulator support allowed local guest OS privileged users to cause a denial of service (NULL pointer dereference and QEMU process crash) by flushing an empty CDROM device drive (bsc#1054724)\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote attackers to cause a denial of service (daemon crash) by disconnecting during a server-to-client reply attempt (bsc#1046636)\n- CVE-2017-10806: Stack-based buffer overflow allowed local guest OS users to cause a denial of service (QEMU process crash) via vectors related to logging debug messages (bsc#1047674)\n- CVE-2017-14167: Integer overflow in the load_multiboot function allowed local guest OS users to execute arbitrary code on the host via crafted multiboot header address values, which trigger an out-of-bounds write (bsc#1057585)\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP options string (bsc#1049381)\n- CVE-2017-11334: The address_space_write_continue function allowed local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area (bsc#1048902)\n- CVE-2017-13672: The VGA display emulator support allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors involving display update (bsc#1056334)\n\nThese non-security issues were fixed:\n\n- Fixed not being able to build from rpm sources due to undefined macro (bsc#1057966)\n- Fixed wrong permissions for kvm_stat.1 file\n- Fixed KVM lun resize not working as expected on SLES12 SP2 HV (bsc#1043176)\n","status":"published","published":"2017-11-06T16:18:59Z","modified":"2025-05-02T04:06:04.666384Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2946-1","title":"Security update for qemu","description":"This update for qemu fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-10911: The make_response function in the Linux kernel allowed guest OS users to obtain sensitive information from host OS (or other guest OS) kernel memory by leveraging the copying of uninitialized padding fields in Xen block-interface response structures (bsc#1057378).\n- CVE-2017-12809: The IDE disk and CD/DVD-ROM Emulator support allowed local guest OS privileged users to cause a denial of service (NULL pointer dereference and QEMU process crash) by flushing an empty CDROM device drive (bsc#1054724).\n- CVE-2017-15289: The mode4and5 write functions allowed local OS guest privileged users to cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst calculation (bsc#1063122)\n- CVE-2017-15038: Race condition in the v9fs_xattrwalk function local guest OS users to obtain sensitive information from host heap memory via vectors related to reading extended attributes (bsc#1062069)\n- CVE-2017-14167: Integer overflow in the load_multiboot function allowed local guest OS users to execute arbitrary code on the host via crafted multiboot header address values, which trigger an out-of-bounds write (bsc#1057585)\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP options string (bsc#1049381)\n- CVE-2017-11334: The address_space_write_continue function allowed local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area (bsc#1048902)\n- CVE-2017-13672: The VGA display emulator support allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors involving display update (bsc#1056334)\n- CVE-2017-5973: A infinite loop while doing control transfer in xhci_kick_epctx allowed privileged user inside the guest to crash the host process resulting in DoS (bsc#1025109)\n- CVE-2017-5987: The sdhci_sdma_transfer_multi_blocks function in hw/sd/sdhci.c allowed local OS guest privileged users to cause a denial of service (infinite loop and QEMU process crash) via vectors involving the transfer mode register during multi block transfer (bsc#1025311)\n- CVE-2017-6505: The ohci_service_ed_list function allowed local guest OS users to cause a denial of service (infinite loop) via vectors involving the number of link endpoint list descriptors (bsc#1028184)\n- CVE-2016-9603: A privileged user within the guest VM could have caused a heap overflow in the device model process, potentially escalating their privileges to that of the device model process (bsc#1028656)\n- CVE-2017-7718: hw/display/cirrus_vga_rop.h allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors related to copying VGA data via the cirrus_bitblt_rop_fwd_transp_ and cirrus_bitblt_rop_fwd_ functions (bsc#1034908)\n- CVE-2017-7980: An out-of-bounds r/w access issues in the Cirrus CLGD 54xx VGA Emulator support allowed privileged user inside guest to use this flaw to crash the Qemu process resulting in DoS or potentially execute arbitrary code on a host with privileges of Qemu process on the host (bsc#1035406)\n- CVE-2017-8112: hw/scsi/vmw_pvscsi.c allowed local guest OS privileged users to cause a denial of service (infinite loop and CPU consumption) via the message ring page count (bsc#1036211)\n- CVE-2017-9375: The USB xHCI controller emulator support was vulnerable to an infinite recursive call loop issue, which allowed a privileged user inside guest to crash the Qemu process resulting in DoS (bsc#1042800)\n- CVE-2017-9374: Missing free of 's-\u003eipacket', causes a host memory leak, allowing for DoS (bsc#1043073)\n- CVE-2017-9373: The IDE AHCI Emulation support was vulnerable to a host memory leakage issue, which allowed a privileged user inside guest to leak host memory resulting in DoS (bsc#1042801)\n- CVE-2017-9330: USB OHCI Emulation in qemu allowed local guest OS users to cause a denial of service (infinite loop) by leveraging an incorrect return value (bsc#1042159)\n- CVE-2017-8379: Memory leak in the keyboard input event handlers support allowed local guest OS privileged users to cause a denial of service (host memory consumption) by rapidly generating large keyboard events (bsc#1037334)\n- CVE-2017-8309: Memory leak in the audio/audio.c allowed remote attackers to cause a denial of service (memory consumption) by repeatedly starting and stopping audio capture (bsc#1037242)\n- CVE-2017-8380: The MegaRAID SAS 8708EM2 Host Bus Adapter emulation support was vulnerable to an out-of-bounds read access issue which allowed a privileged user inside guest to read host memory resulting in DoS (bsc#1037336)\n- CVE-2017-7493: The VirtFS, host directory sharing via Plan 9 File System(9pfs) support, was vulnerable to an improper access control issue. It could occur while accessing virtfs metadata files in mapped-file security mode. A guest user could have used this flaw to escalate their privileges inside guest (bsc#1039495)\n- CVE-2016-9602: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper link following issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1020427)\n- CVE-2017-5579: The 16550A UART serial device emulation support was vulnerable to a memory leakage issue allowing a privileged user to cause a DoS and/or potentially crash the Qemu process on the host (bsc#1021741)\n- CVE-2017-9503: The MegaRAID SAS 8708EM2 Host Bus Adapter emulation support was vulnerable to a null pointer dereference issue which allowed a privileged user inside guest to crash the Qemu process on the host resulting in DoS (bsc#1043296)\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote attackers to cause a denial of service (daemon crash) by disconnecting during a server-to-client reply attempt (bsc#1046636)\n- CVE-2017-10806: Stack-based buffer overflow allowed local guest OS users to cause a denial of service (QEMU process crash) via vectors related to logging debug messages (bsc#1047674)\n- CVE-2016-9602: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper link following issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1020427)\n- CVE-2017-7377: The v9fs_create and v9fs_lcreate functions in hw/9pfs/9p.c allowed local guest OS privileged users to cause a denial of service (file descriptor or memory consumption) via vectors related to an already in-use fid (bsc#1032075)\n- CVE-2017-8086: A memory leak in the v9fs_list_xattr function in hw/9pfs/9p-xattr.c allowed local guest OS privileged users to cause a denial of service (memory consumption) via vectors involving the orig_value variable (bsc#1035950)\n- CVE-2017-7471: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper access control issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1034866)\n- CVE-2016-6835: Buffer overflow in the VMWARE VMXNET3 NIC device support, causing an OOB read access (bsc#994605)\n- CVE-2016-6834: A infinite loop during packet fragmentation in the VMWARE VMXNET3 NIC device support allowed privileged user inside guest to crash the Qemu instance resulting in DoS (bsc#994418)\n- Fix privilege escalation in TCG mode (bsc#1030624)\n\nThis non-security issue was fixed:\n\n- Fix regression introduced by recent virtfs security fixes (bsc#1045035)\n","status":"published","published":"2017-11-08T07:48:24Z","modified":"2025-05-02T04:05:29.049586Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2963-1","title":"Security update for kvm","description":"This update for kvm fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2016-9602: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper link following issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1020427)\n- CVE-2016-9603: A privileged user within the guest VM could have caused a heap overflow in the device model process, potentially escalating their privileges to that of the device model process (bsc#1028656)\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote attackers to cause a denial of service (daemon crash) by disconnecting during a server-to-client reply attempt (bsc#1046636)\n- CVE-2017-10806: Stack-based buffer overflow allowed local guest OS users to cause a denial of service (QEMU process crash) via vectors related to logging debug messages (bsc#1047674).\n- CVE-2017-11334: The address_space_write_continue function allowed local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area (bsc#1048902).\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP options string (bsc#1049381)\n- CVE-2017-13672: The VGA display emulator support allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors involving display update (bsc#1056334).\n- CVE-2017-14167: Integer overflow in the load_multiboot function allowed local guest OS users to execute arbitrary code on the host via crafted multiboot header address values, which trigger an out-of-bounds write (bsc#1057585).\n- CVE-2017-15038: Race condition in the v9fs_xattrwalk function local guest OS users to obtain sensitive information from host heap memory via vectors related to reading extended attributes (bsc#1062069).\n- CVE-2017-15289: The mode4and5 write functions allowed local OS guest privileged users to cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst calculation (bsc#1063122).\n- CVE-2017-5579: The 16550A UART serial device emulation support was vulnerable to a memory leakage issue allowing a privileged user to cause a DoS and/or potentially crash the Qemu process on the host (bsc#1021741)\n- CVE-2017-5973: A infinite loop while doing control transfer in xhci_kick_epctx allowed privileged user inside the guest to crash the host process resulting in DoS (bsc#1025109)\n- CVE-2017-6505: The ohci_service_ed_list function allowed local guest OS users to cause a denial of service (infinite loop) via vectors involving the number of link endpoint list descriptors (bsc#1028184)\n- CVE-2017-7471: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper access control issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1034866)\n- CVE-2017-7493: The VirtFS, host directory sharing via Plan 9 File System(9pfs) support, was vulnerable to an improper access control issue. It could occur while accessing virtfs metadata files in mapped-file security mode. A guest user could have used this flaw to escalate their privileges inside guest (bsc#1039495)\n- CVE-2017-7718: hw/display/cirrus_vga_rop.h allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors related to copying VGA data via the cirrus_bitblt_rop_fwd_transp_ and cirrus_bitblt_rop_fwd_ functions (bsc#1034908)\n- CVE-2017-7980: An out-of-bounds r/w access issues in the Cirrus CLGD 54xx VGA Emulator support allowed privileged user inside guest to use this flaw to crash the Qemu process resulting in DoS or potentially execute arbitrary code on a host with privileges of Qemu process on the host (bsc#1035406)\n- CVE-2017-8086: A memory leak in the v9fs_list_xattr function in hw/9pfs/9p-xattr.c allowed local guest OS privileged users to cause a denial of service (memory consumption) via vectors involving the orig_value variable (bsc#1035950)\n- CVE-2017-8309: Memory leak in the audio/audio.c allowed remote attackers to cause a denial of service (memory consumption) by repeatedly starting and stopping audio capture (bsc#1037242)\n- CVE-2017-9330: USB OHCI Emulation in qemu allowed local guest OS users to cause a denial of service (infinite loop) by leveraging an incorrect return value (bsc#1042159)\n- CVE-2017-9373: The IDE AHCI Emulation support was vulnerable to a host memory leakage issue, which allowed a privileged user inside guest to leak host memory resulting in DoS (bsc#1042801)\n- CVE-2017-9375: The USB xHCI controller emulator support was vulnerable to an infinite recursive call loop issue, which allowed a privileged user inside guest to crash the Qemu process resulting in DoS (bsc#1042800)\n- CVE-2017-9503: The MegaRAID SAS 8708EM2 Host Bus Adapter emulation support was vulnerable to a null pointer dereference issue which allowed a privileged user inside guest to crash the Qemu process on the host resulting in DoS (bsc#1043296)\n- Privilege escalation in TCG mode (bsc#1030624)\n\nThese non-security issues were fixed:\n\n- bsc#1038396: Fixed 12 tempest tests\n- bsc#1045035: Fixed regression introduced by previous virtfs security fixes\n- bsc#1034044: Prevent KVM guests stuck when waiting for sg_io() completion\n- bsc#1031051: Prevent I/O errors when using pvmove with disk device=lun\n- bsc#1049785: Make virsh dump output readable by crash \n","status":"published","published":"2017-11-09T15:17:11Z","modified":"2026-02-04T03:05:35.260833Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2969-1","title":"Security update for qemu","description":"This update for qemu fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-15289: The mode4and5 write functions allowed local OS guest privileged users to cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst calculation (bsc#1063122)\n- CVE-2017-2633: The VNC display driver support was vulnerable to an out-of-bounds memory access issue. A user/process inside guest could use this flaw to cause DoS (bsc#1026612)\n- CVE-2017-15038: Race condition in the v9fs_xattrwalk function local guest OS users to obtain sensitive information from host heap memory via vectors related to reading extended attributes (bsc#1062069)\n- CVE-2017-14167: Integer overflow in the load_multiboot function allowed local guest OS users to execute arbitrary code on the host via crafted multiboot header address values, which trigger an out-of-bounds write (bsc#1057585)\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP options string (bsc#1049381)\n- CVE-2017-11334: The address_space_write_continue function allowed local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area (bsc#1048902)\n- CVE-2017-13672: The VGA display emulator support allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors involving display update (bsc#1056334)\n- CVE-2017-5973: A infinite loop while doing control transfer in xhci_kick_epctx allowed privileged user inside the guest to crash the host process resulting in DoS (bsc#1025109)\n- CVE-2017-5987: The sdhci_sdma_transfer_multi_blocks function in hw/sd/sdhci.c allowed local OS guest privileged users to cause a denial of service (infinite loop and QEMU process crash) via vectors involving the transfer mode register during multi block transfer (bsc#1025311)\n- CVE-2017-6505: The ohci_service_ed_list function allowed local guest OS users to cause a denial of service (infinite loop) via vectors involving the number of link endpoint list descriptors (bsc#1028184)\n- CVE-2016-9603: A privileged user within the guest VM could have caused a heap overflow in the device model process, potentially escalating their privileges to that of the device model process (bsc#1028656)\n- CVE-2017-7718: hw/display/cirrus_vga_rop.h allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors related to copying VGA data via the cirrus_bitblt_rop_fwd_transp_ and cirrus_bitblt_rop_fwd_ functions (bsc#1034908)\n- CVE-2017-7980: An out-of-bounds r/w access issues in the Cirrus CLGD 54xx VGA Emulator support allowed privileged user inside guest to use this flaw to crash the Qemu process resulting in DoS or potentially execute arbitrary code on a host with privileges of Qemu process on the host (bsc#1035406)\n- CVE-2017-8112: hw/scsi/vmw_pvscsi.c allowed local guest OS privileged users to cause a denial of service (infinite loop and CPU consumption) via the message ring page count (bsc#1036211)\n- CVE-2017-9375: The USB xHCI controller emulator support was vulnerable to an infinite recursive call loop issue, which allowed a privileged user inside guest to crash the Qemu process resulting in DoS (bsc#1042800)\n- CVE-2017-9373: The IDE AHCI Emulation support was vulnerable to a host memory leakage issue, which allowed a privileged user inside guest to leak host memory resulting in DoS (bsc#1042801)\n- CVE-2017-9330: USB OHCI Emulation in qemu allowed local guest OS users to cause a denial of service (infinite loop) by leveraging an incorrect return value (bsc#1042159)\n- CVE-2017-8309: Memory leak in the audio/audio.c allowed remote attackers to cause a denial of service (memory consumption) by repeatedly starting and stopping audio capture (bsc#1037242)\n- CVE-2017-7493: The VirtFS, host directory sharing via Plan 9 File System(9pfs) support, was vulnerable to an improper access control issue. It could occur while accessing virtfs metadata files in mapped-file security mode. A guest user could have used this flaw to escalate their privileges inside guest (bsc#1039495)\n- CVE-2016-9602: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper link following issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1020427)\n- CVE-2017-5579: The 16550A UART serial device emulation support was vulnerable to a memory leakage issue allowing a privileged user to cause a DoS and/or potentially crash the Qemu process on the host (bsc#1021741)\n- CVE-2017-9503: The MegaRAID SAS 8708EM2 Host Bus Adapter emulation support was vulnerable to a null pointer dereference issue which allowed a privileged user inside guest to crash the Qemu process on the host resulting in DoS (bsc#1043296)\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote attackers to cause a denial of service (daemon crash) by disconnecting during a server-to-client reply attempt (bsc#1046636)\n- CVE-2017-10806: Stack-based buffer overflow allowed local guest OS users to cause a denial of service (QEMU process crash) via vectors related to logging debug messages (bsc#1047674)\n- CVE-2016-9602: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper link following issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1020427)\n- CVE-2017-7377: The v9fs_create and v9fs_lcreate functions in hw/9pfs/9p.c allowed local guest OS privileged users to cause a denial of service (file descriptor or memory consumption) via vectors related to an already in-use fid (bsc#1032075)\n- CVE-2017-8086: A memory leak in the v9fs_list_xattr function in hw/9pfs/9p-xattr.c allowed local guest OS privileged users to cause a denial of service (memory consumption) via vectors involving the orig_value variable (bsc#1035950)\n- CVE-2017-7471: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper access control issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1034866)\n- CVE-2016-6834: A infinite loop during packet fragmentation in the VMWARE VMXNET3 NIC device support allowed privileged user inside guest to crash the Qemu instance resulting in DoS (bsc#994418)\n- CVE-2016-6835: Buffer overflow in the VMWARE VMXNET3 NIC device support, causing an OOB read access (bsc#994605)\n- Fix privilege escalation in TCG mode (bsc#1030624)\n\nThis non-security issue wsa fixed:\n\n* bsc#1045035: Fix regression introduced by former virtfs security fixes \n","status":"published","published":"2017-11-09T15:17:28Z","modified":"2026-02-04T03:30:24.008774Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:3084-1","title":"Security update for kvm","description":"\nThis update for kvm fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-2620: In CIRRUS_BLTMODE_MEMSYSSRC mode the bitblit copy routine cirrus_bitblt_cputovideo failed to check the memory region, allowing for an out-of-bounds write that allows for privilege escalation (bsc#1024972)\n- CVE-2017-2615: An error in the bitblt copy operation could have allowed a malicious guest administrator to cause an out of bounds memory access, possibly leading to information disclosure or privilege escalation (bsc#1023004)\n- CVE-2016-9776: The ColdFire Fast Ethernet Controller emulator support was vulnerable to an infinite loop issue while receiving packets in 'mcf_fec_receive'. A privileged user/process inside guest could have used this issue to crash the Qemu process on the host leading to DoS (bsc#1013285)\n- CVE-2016-9911: The USB EHCI Emulation support was vulnerable to a memory leakage issue while processing packet data in 'ehci_init_transfer'. A guest user/process could have used this issue to leak host memory, resulting in DoS for the host (bsc#1014111)\n- CVE-2016-9907: The USB redirector usb-guest support was vulnerable to a memory leakage flaw when destroying the USB redirector in 'usbredir_handle_destroy'.  A guest user/process could have used this issue to leak host memory, resulting in DoS for a host (bsc#1014109)\n- CVE-2016-9921: The Cirrus CLGD 54xx VGA Emulator support was vulnerable to a divide by zero issue while copying VGA data. A privileged user inside guest could have used this flaw to crash the process instance on the host, resulting in DoS (bsc#1014702)\n- CVE-2016-9922: The Cirrus CLGD 54xx VGA Emulator support was vulnerable to a divide by zero issue while copying VGA data. A privileged user inside guest could have used this flaw to crash the process instance on the host, resulting in DoS (bsc#1014702)\n- CVE-2017-5898: The CCID Card device emulator support was vulnerable to an integer overflow allowing a privileged user inside the guest to crash the Qemu process resulting in DoS (bnc#1023907)\n- CVE-2016-10155: The virtual hardware watchdog 'wdt_i6300esb' was vulnerable to a memory leakage issue allowing a privileged user to cause a DoS and/or potentially crash the Qemu process on the host (bsc#1021129)\n- CVE-2017-5856: The MegaRAID SAS 8708EM2 Host Bus Adapter emulation support was vulnerable to a memory leakage issue allowing a privileged user to leak host memory resulting in DoS (bsc#1023053)\n- CVE-2016-9602: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper link following issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1020427)\n- CVE-2016-9603: A privileged user within the guest VM could have caused a heap overflow in the device model process, potentially escalating their privileges to that of the device model process (bsc#1028656)\n- CVE-2017-10664: qemu-nbd did not ignore SIGPIPE, which allowed remote attackers to cause a denial of service (daemon crash) by disconnecting during a server-to-client reply attempt (bsc#1046636)\n- CVE-2017-10806: Stack-based buffer overflow allowed local guest OS users to cause a denial of service (QEMU process crash) via vectors related to logging debug messages (bsc#1047674)\n- CVE-2017-11334: The address_space_write_continue function allowed local guest OS privileged users to cause a denial of service (out-of-bounds access and guest instance crash) by leveraging use of qemu_map_ram_ptr to access guest ram block area (bsc#1048902)\n- CVE-2017-11434: The dhcp_decode function in slirp/bootp.c allowed local guest OS users to cause a denial of service (out-of-bounds read) via a crafted DHCP options string (bsc#1049381)\n- CVE-2017-13672: The VGA display emulator support allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors involving display update (bsc#1056334)\n- CVE-2017-14167: Integer overflow in the load_multiboot function allowed local guest OS users to execute arbitrary code on the host via crafted multiboot header address values, which trigger an out-of-bounds write (bsc#1057585)\n- CVE-2017-15038: Race condition in the v9fs_xattrwalk function local guest OS users to obtain sensitive information from host heap memory via vectors related to reading extended attributes (bsc#1062069)\n- CVE-2017-15289: The mode4and5 write functions allowed local OS guest privileged users to cause a denial of service (out-of-bounds write access and Qemu process crash) via vectors related to dst calculation (bsc#1063122)\n- CVE-2017-5579: The 16550A UART serial device emulation support was vulnerable to a memory leakage issue allowing a privileged user to cause a DoS and/or potentially crash the Qemu process on the host (bsc#1021741)\n- CVE-2017-5973: A infinite loop while doing control transfer in xhci_kick_epctx allowed privileged user inside the guest to crash the host process resulting in DoS (bsc#1025109)\n- CVE-2017-6505: The ohci_service_ed_list function allowed local guest OS users to cause a denial of service (infinite loop) via vectors involving the number of link endpoint list descriptors (bsc#1028184)\n- CVE-2017-7471: The VirtFS host directory sharing via Plan 9 File System(9pfs) support was vulnerable to an improper access control issue which allowed a privileged user inside guest to access host file system beyond the shared folder and potentially escalating their privileges on a host (bsc#1034866)\n- CVE-2017-7493: The VirtFS, host directory sharing via Plan 9 File System(9pfs) support, was vulnerable to an improper access control issue. It could occur while accessing virtfs metadata files in mapped-file security mode. A guest user could have used this flaw to escalate their privileges inside guest (bsc#1039495)\n- CVE-2017-7718: hw/display/cirrus_vga_rop.h allowed local guest OS privileged users to cause a denial of service (out-of-bounds read and QEMU process crash) via vectors related to copying VGA data via the cirrus_bitblt_rop_fwd_transp_ and cirrus_bitblt_rop_fwd_ functions (bsc#1034908)\n- CVE-2017-7980: An out-of-bounds r/w access issues in the Cirrus CLGD 54xx VGA Emulator support allowed privileged user inside guest to use this flaw to crash the Qemu process resulting in DoS or potentially execute arbitrary code on a host with privileges of Qemu process on the host (bsc#1035406)\n- CVE-2017-8086: A memory leak in the v9fs_list_xattr function in hw/9pfs/9p-xattr.c allowed local guest OS privileged users to cause a denial of service (memory consumption) via vectors involving the orig_value variable (bsc#1035950)\n- CVE-2017-8309: Memory leak in the audio/audio.c allowed remote attackers to cause a denial of service (memory consumption) by repeatedly starting and stopping audio capture (bsc#1037242)\n- CVE-2017-9330: USB OHCI Emulation in qemu allowed local guest OS users to cause a denial of service (infinite loop) by leveraging an incorrect return value (bsc#1042159)\n- CVE-2017-9373: The IDE AHCI Emulation support was vulnerable to a host memory leakage issue, which allowed a privileged user inside guest to leak host memory resulting in DoS (bsc#1042801)\n- CVE-2017-9375: The USB xHCI controller emulator support was vulnerable to an infinite recursive call loop issue, which allowed a privileged user inside guest to crash the Qemu process resulting in DoS (bsc#1042800)\n- CVE-2017-9503: The MegaRAID SAS 8708EM2 Host Bus Adapter emulation support was vulnerable to a null pointer dereference issue which allowed a privileged user inside guest to crash the Qemu process on the host resulting in DoS (bsc#1043296)\n* Fix privilege escalation in TCG mode (bsc#1030624)\n\nThese non-security issues were fixed:\n\n- bsc#1045035: Fixed regression introduced by previous virtfs security fixes\n- bsc#1038396: Fixed 12 tempest tests\n- bsc#1034044: Prevent KVM guests stuck when waiting for sg_io() completion\n- bsc#1031051: Prevent I/O errors when using pvmove with disk device=lun\n- bsc#1049785: Make virsh dump output readable by crash\n- bsc#1015048: Fixed virtio interface failure \n- bsc#1016779: Fixed graphical update errors introduced by previous security fix\n- Fixed various inaccuracies in cirrus vga device emulation\n","status":"published","published":"2017-11-24T15:21:30Z","modified":"2026-02-04T02:55:25.137009Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2018:0678-1","title":"Security update for xen","description":"This update for xen fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-5753, CVE-2017-5715, CVE-2017-5754: Prevent information leaks via\n  side effects of speculative execution, aka 'Spectre' and 'Meltdown' attacks\n  (bsc#1074562, bsc#1068032)\n- CVE-2018-5683: The vga_draw_text function allowed local OS guest privileged\n  users to cause a denial of service (out-of-bounds read and QEMU process crash)\n  by leveraging improper memory address validation (bsc#1076116).\n- CVE-2017-18030: The cirrus_invalidate_region function allowed local OS guest\n  privileged users to cause a denial of service (out-of-bounds array access and\n  QEMU process crash) via vectors related to negative pitch (bsc#1076180).\n- CVE-2017-15595: x86 PV guest OS users were able to cause a DoS (unbounded\n  recursion, stack consumption, and hypervisor crash) or possibly gain privileges\n  via crafted page-table stacking (bsc#1061081)\n- CVE-2017-17566: Prevent PV guest OS users to cause a denial of service (host\n  OS crash) or gain host OS privileges in shadow mode by mapping a certain\n  auxiliary page (bsc#1070158).\n- CVE-2017-17563: Prevent guest OS users to cause a denial of service (host OS\n  crash) or gain host OS privileges by leveraging an incorrect mask for\n  reference-count overflow checking in shadow mode (bsc#1070159).\n- CVE-2017-17564: Prevent guest OS users to cause a denial of service (host OS\n  crash) or gain host OS privileges by leveraging incorrect error handling for\n  reference counting in shadow mode (bsc#1070160).\n- CVE-2017-17565: Prevent PV guest OS users to cause a denial of service (host\n  OS crash) if shadow mode and log-dirty mode are in place, because of an\n  incorrect assertion related to M2P (bsc#1070163).\n- Added missing intermediate preemption checks for guest requesting removal of\n  memory. This allowed malicious guest administrator to cause denial of service\n  due to the high cost of this operation (bsc#1080635).\n- Because of XEN not returning the proper error messages when transitioning\n  grant tables from v2 to v1 a malicious guest was able to cause DoS or\n  potentially allowed for privilege escalation as well as information leaks\n  (bsc#1080662).\n- CVE-2017-5898: The CCID Card device emulator support was vulnerable to an\n  integer overflow flaw allowing a privileged user to crash the Qemu process on\n  the host resulting in DoS (bsc#1024307)\n- Unprivileged domains could have issued well-timed writes to xenstore which\n  conflict with transactions to stall progress of the control domain or driver\n  domain, possibly leading to DoS (bsc#1030144, XSA-206).\n","status":"published","published":"2018-03-14T17:37:06Z","modified":"2026-02-04T03:15:35.836035Z","updated_at":"2026-11-02T15:53:44.594517Z"},{"id":"USN-3575-1","title":"qemu vulnerabilities","description":"It was discovered that QEMU incorrectly handled guest ram. A privileged\nattacker inside the guest could use this issue to cause QEMU to crash,\nresulting in a denial of service. This issue only affected Ubuntu 14.04 LTS\nand Ubuntu 16.04 LTS. (CVE-2017-11334)\n\nDavid Buchanan discovered that QEMU incorrectly handled the VGA device. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. This issue was only addressed in\nUbuntu 17.10. (CVE-2017-13672)\n\nThomas Garnier discovered that QEMU incorrectly handled multiboot. An\nattacker could use this issue to cause QEMU to crash, resulting in a denial\nof service, or possibly execute arbitrary code on the host. In the default\ninstallation, when QEMU is used with libvirt, attackers would be isolated\nby the libvirt AppArmor profile. This issue only affected Ubuntu 14.04 LTS\nand Ubuntu 16.04 LTS. (CVE-2017-14167)\n\nTuomas Tynkkynen discovered that QEMU incorrectly handled VirtFS directory\nsharing. An attacker could use this issue to obtain sensitive information\nfrom host memory. (CVE-2017-15038)\n\nEric Blake discovered that QEMU incorrectly handled memory in the\nNBD server. An attacker could use this issue to cause the NBD server to\ncrash, resulting in a denial of service. This issue only affected Ubuntu\n17.10. (CVE-2017-15118)\n\nEric Blake discovered that QEMU incorrectly handled certain options to the\nNBD server. An attacker could use this issue to cause the NBD server to\ncrash, resulting in a denial of service. This issue only affected Ubuntu\n14.04 LTS and Ubuntu 16.04 LTS. (CVE-2017-15119)\n\nDaniel Berrange discovered that QEMU incorrectly handled the VNC server. A\nremote attacker could possibly use this issue to consume memory, resulting\nin a denial of service. This issue was only addressed in Ubuntu 17.10.\n(CVE-2017-15124)\n\nCarl Brassey discovered that QEMU incorrectly handled certain websockets. A\nremote attacker could possibly use this issue to consume memory, resulting\nin a denial of service. This issue only affected Ubuntu 17.10.\n(CVE-2017-15268)\n\nGuoxiang Niu discovered that QEMU incorrectly handled the Cirrus VGA\ndevice. A privileged attacker inside the guest could use this issue to\ncause QEMU to crash, resulting in a denial of service. (CVE-2017-15289)\n\nCyrille Chatras discovered that QEMU incorrectly handled certain PS2 values\nduring migration. An attacker could possibly use this issue to cause QEMU\nto crash, resulting in a denial of service, or possibly execute arbitrary\ncode. This issue only affected Ubuntu 16.04 LTS and Ubuntu 17.10.\n(CVE-2017-16845)\n\nIt was discovered that QEMU incorrectly handled the Virtio Vring\nimplementation. An attacker could possibly use this issue to cause QEMU to\ncrash, resulting in a denial of service. This issue only affected Ubuntu\n16.04 LTS and Ubuntu 17.10. (CVE-2017-17381)\n\nEric Blake discovered that QEMU incorrectly handled certain rounding\noperations. An attacker could possibly use this issue to cause QEMU to\ncrash, resulting in a denial of service. This issue only affected Ubuntu\n14.04 LTS and Ubuntu 16.04 LTS. (CVE-2017-18043)\n\nJiang Xin and Lin ZheCheng discovered that QEMU incorrectly handled the\nVGA device. A privileged attacker inside the guest could use this issue to\ncause QEMU to crash, resulting in a denial of service. (CVE-2018-5683)\n","status":"published","published":"2018-02-20T19:12:03Z","modified":"2026-02-10T04:41:16Z","updated_at":"2026-11-02T16:58:13.496563Z"}]}}