CVE Vulnerabilities

CVE-2017-5579

Missing Release of Memory after Effective Lifetime

Published: Mar 15, 2017 | Modified: Feb 12, 2023
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
CVSS 2.x
4.9 MEDIUM
AV:L/AC:L/Au:N/C:N/I:N/A:C
RedHat/V2
2.3 LOW
AV:A/AC:M/Au:S/C:N/I:N/A:P
RedHat/V3
4.1 LOW
CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:L
Ubuntu
LOW

Memory leak in the serial_exit_core function in hw/char/serial.c in QEMU (aka Quick Emulator) allows local guest OS privileged users to cause a denial of service (host memory consumption and QEMU process crash) via a large number of device unplug operations.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

Affected Software

Name Vendor Start Version End Version
Qemu Qemu * 2.8.1.1 (including)
Qemu Qemu 2.9.0-rc0 (including) 2.9.0-rc0 (including)
Qemu Qemu 2.9.0-rc1 (including) 2.9.0-rc1 (including)
Qemu Qemu 2.9.0-rc2 (including) 2.9.0-rc2 (including)
Qemu Qemu 2.9.0-rc3 (including) 2.9.0-rc3 (including)
Qemu Qemu 2.9.0-rc4 (including) 2.9.0-rc4 (including)
Qemu Qemu 2.9.0-rc5 (including) 2.9.0-rc5 (including)
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7 RedHat qemu-kvm-rhev-10:2.9.0-10.el7 *
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7 RedHat qemu-kvm-rhev-10:2.9.0-10.el7 *
Red Hat OpenStack Platform 10.0 (Newton) RedHat qemu-kvm-rhev-10:2.9.0-10.el7 *
Red Hat OpenStack Platform 11.0 (Ocata) RedHat qemu-kvm-rhev-10:2.9.0-10.el7 *
Red Hat OpenStack Platform 8.0 (Liberty) RedHat qemu-kvm-rhev-10:2.9.0-10.el7 *
Red Hat OpenStack Platform 9.0 (Mitaka) RedHat qemu-kvm-rhev-10:2.9.0-10.el7 *
Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 RedHat qemu-kvm-rhev-10:2.9.0-14.el7 *
Qemu Ubuntu trusty *
Qemu Ubuntu xenial *
Qemu Ubuntu yakkety *
Qemu-kvm Ubuntu precise *
Qemu-kvm Ubuntu precise/esm *

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