Memory leak in the virtio_gpu_set_scanout function in hw/display/virtio-gpu.c in QEMU (aka Quick Emulator) allows local guest OS users to cause a denial of service (memory consumption) via a large number of VIRTIO_GPU_CMD_SET_SCANOUT: commands.
Weakness
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Qemu | Qemu | * | 2.8.1.1 (including) |
| Qemu | Ubuntu | upstream | * |
| Qemu | Ubuntu | yakkety | * |
| Qemu | Ubuntu | zesty | * |
| Qemu-kvm | Ubuntu | upstream | * |
Potential Mitigations
- Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
- For example, glibc in Linux provides protection against free of invalid pointers.
- When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
- To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.
References
- http://git.qemu.org/?p=qemu.git%3Ba=commit%3Bh=dd248ed7e204ee8a1873914e02b8b526e8f1b80d
- http://www.openwall.com/lists/oss-security/2017/05/19/1
- http://www.securityfocus.com/bid/98632
- https://bugzilla.redhat.com/show_bug.cgi?id=1452597
- https://security.gentoo.org/glsa/201706-03
- http://git.qemu.org/?p=qemu.git%3Ba=commit%3Bh=dd248ed7e204ee8a1873914e02b8b526e8f1b80d
- http://www.openwall.com/lists/oss-security/2017/05/19/1
- http://www.securityfocus.com/bid/98632
- https://bugzilla.redhat.com/show_bug.cgi?id=1452597
- https://security.gentoo.org/glsa/201706-03