{"id":"CVE-2017-5578","aliases":["ALPINE-CVE-2017-5578","BELL-CVE-2017-5578","DEBIAN-CVE-2017-5578","EUVD-2017-14679","GHSA-q2vm-m3p4-mpg8","SUSE-SU-2017:0625-1","UBUNTU-CVE-2017-5578","USN-3261-1","openSUSE-SU-2024:11287-1"],"status":"published","title":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU...","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-08","score":0.00398,"percentile":0.34259,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-401"],"published":"2017-03-07T12:59:04Z","modified":"2026-10-24T10:31:01Z","fixes":[{"ecosystem":"Alpine:v3.10","package":"qemu","fixed_in":["2.8.1-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.5","package":"qemu","fixed_in":["2.8.1.1-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.6","package":"qemu","fixed_in":["2.8.1-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.7","package":"qemu","fixed_in":["2.8.1-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.8","package":"qemu","fixed_in":["2.8.1-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.9","package":"qemu","fixed_in":["2.8.1-r1"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"qemu","fixed_in":["1:2.10.0-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"qemu","fixed_in":["1:2.10.0-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"qemu","fixed_in":["1:2.10.0-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"qemu","fixed_in":["1:2.5+dfsg-5ubuntu10.11"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.10","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.1-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.5","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.1.1-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.6","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.1-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.7","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.1-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.8","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.1-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.9","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.8.1-r1"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.10.0-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.10.0-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.10.0-1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.9.1"}]}],"bundled":15},{"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.9.1"}]}],"bundled":15},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.9.1"}]}],"bundled":15},{"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.9.1"}]}],"bundled":15},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.5+dfsg-5ubuntu10.11"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0+dfsg-2ubuntu1.33"}]}],"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"],"bundled":37},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.5+dfsg-5ubuntu10.11"}]}],"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"],"bundled":37},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.0-32.1"}]}],"bundled":135}],"products":[{"vendor":"qemu","product":"qemu"}],"references":[{"url":"http://git.qemu.org/?p=qemu.git%3Ba=commit%3Bh=204f01b30975923c64006f8067f0937b91eea68b","tags":["x_refsource_CONFIRM","x_transferred","web"]},{"url":"http://www.securityfocus.com/bid/95781","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://security.gentoo.org/glsa/201702-28","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","Third Party Advisory","advisory"]},{"url":"http://www.openwall.com/lists/oss-security/2017/01/23/3","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Patch","Third Party Advisory","fix"]},{"url":"http://www.openwall.com/lists/oss-security/2017/01/25/2","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Patch","Third Party Advisory","fix"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-5578"},{"url":"http://git.qemu.org/?p=qemu.git;a=commit;h=204f01b30975923c64006f8067f0937b91eea68b"},{"url":"https://github.com/advisories/GHSA-q2vm-m3p4-mpg8"},{"url":"https://security.alpinelinux.org/vuln/CVE-2017-5578","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2017-5578","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-5578","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20170625-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1014702","tags":["report"]},{"url":"https://bugzilla.suse.com/1015169","tags":["report"]},{"url":"https://bugzilla.suse.com/1016779","tags":["report"]},{"url":"https://bugzilla.suse.com/1017081","tags":["report"]},{"url":"https://bugzilla.suse.com/1017084","tags":["report"]},{"url":"https://bugzilla.suse.com/1020491","tags":["report"]},{"url":"https://bugzilla.suse.com/1020589","tags":["report"]},{"url":"https://bugzilla.suse.com/1020928","tags":["report"]},{"url":"https://bugzilla.suse.com/1021129","tags":["report"]},{"url":"https://bugzilla.suse.com/1021195","tags":["report"]},{"url":"https://bugzilla.suse.com/1021481","tags":["report"]},{"url":"https://bugzilla.suse.com/1022541","tags":["report"]},{"url":"https://bugzilla.suse.com/1023004","tags":["report"]},{"url":"https://bugzilla.suse.com/1023053","tags":["report"]},{"url":"https://bugzilla.suse.com/1023073","tags":["report"]},{"url":"https://bugzilla.suse.com/1023907","tags":["report"]},{"url":"https://bugzilla.suse.com/1024972","tags":["report"]},{"url":"https://bugzilla.suse.com/1026583","tags":["report"]},{"url":"https://bugzilla.suse.com/977027","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2016-10028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-10029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-10155","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-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-5856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5898","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2017-5578","tags":["report"]},{"url":"http://openwall.com/lists/oss-security/2017/01/25/2","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3261-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3268-1","tags":["advisory"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-5578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-7907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-8667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-8669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9381","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9603","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9908","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-9922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-10028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-10029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2016-10155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2620","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-2633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5525","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5667","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-5987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-6505","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-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-2016-9602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9907","tags":["web"]},{"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-13673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13711","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-15118","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-2630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6058","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-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-9503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9524","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-5578","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2017-03-15T15:00:00Z","modified":"2024-08-05T15:04:15.493Z","updated_at":"2026-11-02T14:33:12.599234Z"}],"euvd":[{"id":"EUVD-2017-14679","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2017-03-15T15:00:00Z","modified":"2024-08-05T15:04:15Z","updated_at":"2026-11-03T02:39:15.385305Z"}],"ghsa":[{"id":"GHSA-q2vm-m3p4-mpg8","title":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU...","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2022-05-13T01:13:40Z","modified":"2023-02-13T00:31:02Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-401"],"updated_at":"2026-11-02T14:54:05.462623Z"}],"nvd":[{"id":"CVE-2017-5578","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2017-03-15T15:59:00.843Z","modified":"2026-06-17T01:20:46.543Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium","assessor":"primary"},{"version":"2.0","score":4.9,"vector":"AV:L/AC:L/Au:N/C:N/I:N/A:C","level":"medium","assessor":"primary"}],"cwes":["CWE-401"],"updated_at":"2026-11-02T14:03:44.275273Z"}],"osv":[{"id":"ALPINE-CVE-2017-5578","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2017-03-15T15:59:00.843Z","modified":"2026-06-15T18:24:50.669894567Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:27:46.716249Z"},{"id":"BELL-CVE-2017-5578","title":"CVE-2017-5578 does not affect BellSoft software","status":"withdrawn","published":"2023-08-31T12:15:37.164668Z","modified":"2026-01-26T09:48:54.807293Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:14.137943Z"},{"id":"CVE-2017-5578","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2017-03-15T15:59:00.843Z","modified":"2026-10-24T10:31:01.679021509Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:44:06.029968Z"},{"id":"DEBIAN-CVE-2017-5578","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2017-03-15T15:59:00.843Z","modified":"2026-09-01T20:03:48.603141256Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:45:29.412243Z"},{"id":"UBUNTU-CVE-2017-5578","description":"Memory leak in the virtio_gpu_resource_attach_backing function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (host memory consumption) via a large number of VIRTIO_GPU_CMD_RESOURCE_ATTACH_BACKING commands.","status":"published","published":"2017-03-15T00:00:00Z","modified":"2026-02-04T02:19:39.681087Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium"},{"version":"3.0","score":6.5,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:54:15.388065Z"},{"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:0625-1","title":"Security update for qemu","description":"\nThis update for qemu fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-5898: The CCID Card device emulator support was vulnerable to an integer overflow flaw allowing a privileged user to crash the Qemu process on the host resulting in DoS (bsc#1023907).\n- CVE-2017-5857: The Virtio GPU Device emulator support was vulnerable to a host memory leakage issue allowing a guest user to leak host memory resulting in DoS (bsc#1023073).\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-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-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-2016-10029: The Virtio GPU Device emulator support was vulnerable to an OOB read issue allowing a guest user to crash the Qemu process instance resulting in Dos (bsc#1017081).\n- CVE-2016-10028: The Virtio GPU Device emulator support was vulnerable to an out of bounds memory access issue allowing a guest user to crash the Qemu process instance on a host, resulting in DoS (bsc#1017084).\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-5552: The Virtio GPU Device emulator support was vulnerable to a memory leakage issue allowing a guest user to leak host memory resulting in DoS (bsc#1021195).\n- CVE-2017-5578: The Virtio GPU Device emulator support was vulnerable to a memory leakage issue allowing a guest user to leak host memory resulting in DoS (bsc#1021481).\n- CVE-2017-5526: The ES1370 audio device emulation support was vulnerable to a memory leakage issue allowing a privileged user inside the guest to cause a DoS and/or potentially crash the Qemu process on the host (bsc#1020589).\n- CVE-2017-5525: The ac97 audio device emulation support was vulnerable to a memory leakage issue allowing a privileged user inside the guest to cause a DoS and/or potentially crash the Qemu process on the host (bsc#1020491).\n- CVE-2017-5667: The SDHCI device emulation support was vulnerable to an OOB heap access issue allowing a privileged user inside the guest to crash the Qemu process resulting in DoS or potentially execute arbitrary code with privileges of the Qemu process on the host (bsc#1022541).\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\nThese non-security issues were fixed:\n\n- Fix name of s390x specific sysctl configuration file to end with .conf (bsc#1026583)\n- XHCI fixes (bsc#977027)\n- Fixed rare race during s390x guest reboot\n- Fixed various inaccuracies in cirrus vga device emulation\n- Fixed cause of infrequent migration failures from bad virtio device state (bsc#1020928)\n- Fixed graphical update errors introduced by previous security fix (bsc#1016779)\n","status":"published","published":"2017-03-07T12:59:04Z","modified":"2026-02-04T03:48:50.673393Z","updated_at":"2026-11-02T15:53:43.83457Z"},{"id":"USN-3261-1","title":"qemu vulnerabilities","description":"Zhenhao Hong discovered that QEMU incorrectly handled the Virtio GPU\ndevice. An attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. This issue only affected Ubuntu\n16.04 LTS and Ubuntu 16.10. (CVE-2016-10028, CVE-2016-10029)\n\nLi Qiang discovered that QEMU incorrectly handled the 6300esb watchdog. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. (CVE-2016-10155)\n\nLi Qiang discovered that QEMU incorrectly handled the i.MX Fast Ethernet\nController. A privileged attacker inside the guest could use this issue to\ncause QEMU to crash, resulting in a denial of service. This issue only\naffected Ubuntu 16.04 LTS and Ubuntu 16.10. (CVE-2016-7907)\n\nIt was discovered that QEMU incorrectly handled the JAZZ RC4030 device. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. (CVE-2016-8667)\n\nIt was discovered that QEMU incorrectly handled the 16550A UART device. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. (CVE-2016-8669)\n\nIt was discovered that QEMU incorrectly handled the shared rings when used\nwith Xen. A privileged attacker inside the guest could use this issue to\ncause QEMU to crash, resulting in a denial of service, or possibly execute\narbitrary code on the host. (CVE-2016-9381)\n\nJann Horn discovered that QEMU incorrectly handled VirtFS directory\nsharing. A privileged attacker inside the guest could use this issue to\naccess files on the host file system outside of the shared directory and\npossibly escalate their privileges. In the default installation, when QEMU\nis used with libvirt, attackers would be isolated by the libvirt AppArmor\nprofile. (CVE-2016-9602)\n\nGerd Hoffmann discovered that QEMU incorrectly handled the Cirrus VGA\ndevice when being used with a VNC connection. A privileged attacker inside\nthe guest could use this issue to cause QEMU to crash, resulting in a\ndenial of service, or possibly execute arbitrary code on the host. In the\ndefault installation, when QEMU is used with libvirt, attackers would be\nisolated by the libvirt AppArmor profile. (CVE-2016-9603)\n\nIt was discovered that QEMU incorrectly handled the ColdFire Fast Ethernet\nController. A privileged attacker inside the guest could use this issue to\ncause QEMU to crash, resulting in a denial of service. (CVE-2016-9776)\n\nLi Qiang discovered that QEMU incorrectly handled the Virtio GPU device. An\nattacker inside the guest could use this issue to cause QEMU to leak\ncontents of host memory. This issue only affected Ubuntu 16.04 LTS and\nUbuntu 16.10. (CVE-2016-9845, CVE-2016-9908)\n\nLi Qiang discovered that QEMU incorrectly handled the Virtio GPU device. An\nattacker inside the guest could use this issue to cause QEMU to crash,\nresulting in a denial of service. This issue only affected Ubuntu 16.04 LTS\nand Ubuntu 16.10. (CVE-2016-9846, CVE-2016-9912, CVE-2017-5552,\nCVE-2017-5578, CVE-2017-5857)\n\nLi Qiang discovered that QEMU incorrectly handled the USB redirector. An\nattacker inside the guest could use this issue to cause QEMU to crash,\nresulting in a denial of service. This issue only affected Ubuntu 16.04 LTS\nand Ubuntu 16.10. (CVE-2016-9907)\n\nLi Qiang discovered that QEMU incorrectly handled USB EHCI emulation. An\nattacker inside the guest could use this issue to cause QEMU to crash,\nresulting in a denial of service. (CVE-2016-9911)\n\nLi Qiang discovered that QEMU incorrectly handled VirtFS directory sharing.\nA privileged attacker inside the guest could use this issue to cause QEMU\nto crash, resulting in a denial of service. (CVE-2016-9913, CVE-2016-9914,\nCVE-2016-9915, CVE-2016-9916)\n\nQinghao Tang, Li Qiang, and Jiangxin discovered that QEMU incorrectly\nhandled the Cirrus VGA device. A privileged attacker inside the guest could\nuse this issue to cause QEMU to crash, resulting in a denial of service.\n(CVE-2016-9921, CVE-2016-9922)\n\nWjjzhang and Li Qiang discovered that QEMU incorrectly handled the Cirrus\nVGA device. A privileged attacker inside the guest could use this issue to\ncause QEMU to crash, resulting in a denial of service, or possibly execute\narbitrary code on the host. In the default installation, when QEMU is used\nwith libvirt, attackers would be isolated by the libvirt AppArmor profile.\n(CVE-2017-2615)\n\nIt was discovered that QEMU incorrectly handled the Cirrus VGA device. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service, or possibly execute arbitrary code\non the host. In the default installation, when QEMU is used with libvirt,\nattackers would be isolated by the libvirt AppArmor profile.\n(CVE-2017-2620)\n\nIt was discovered that QEMU incorrectly handled VNC connections. An\nattacker inside the guest could use this issue to cause QEMU to crash,\nresulting in a denial of service. (CVE-2017-2633)\n\nLi Qiang discovered that QEMU incorrectly handled the ac97 audio device. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. (CVE-2017-5525)\n\nLi Qiang discovered that QEMU incorrectly handled the es1370 audio device.\nA privileged attacker inside the guest could use this issue to cause QEMU\nto crash, resulting in a denial of service. (CVE-2017-5526)\n\nLi Qiang discovered that QEMU incorrectly handled the 16550A UART device. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. (CVE-2017-5579)\n\nJiang Xin discovered that QEMU incorrectly handled SDHCI device emulation.\nA privileged attacker inside the guest could use this issue to cause QEMU\nto crash, resulting in a denial of service, or possibly execute arbitrary\ncode on the host. In the default installation, when QEMU is used with\nlibvirt, attackers would be isolated by the libvirt AppArmor profile.\n(CVE-2017-5667)\n\nLi Qiang discovered that QEMU incorrectly handled the MegaRAID SAS device.\nA privileged attacker inside the guest could use this issue to cause QEMU\nto crash, resulting in a denial of service. (CVE-2017-5856)\n\nLi Qiang discovered that QEMU incorrectly handled the CCID Card device. A\nprivileged attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. (CVE-2017-5898)\n\nLi Qiang discovered that QEMU incorrectly handled USB xHCI controller\nemulation. A privileged attacker inside the guest could use this issue to\ncause QEMU to crash, resulting in a denial of service. (CVE-2017-5973)\n\nJiang Xin and Wjjzhang discovered that QEMU incorrectly handled SDHCI\ndevice emulation. A privileged attacker inside the guest could use this\nissue to cause QEMU to crash, resulting in a denial of service.\n(CVE-2017-5987)\n\nLi Qiang discovered that QEMU incorrectly handled USB OHCI controller\nemulation. A privileged attacker inside the guest could use this issue to\ncause QEMU to hang, resulting in a denial of service. (CVE-2017-6505)\n","status":"published","published":"2017-04-20T18:33:13Z","modified":"2026-02-10T04:41:06Z","updated_at":"2026-11-02T16:58:10.303275Z"}]}}