What is the severity of CVE-2017-5525?

CVE-2017-5525 is classified as a denial of service vulnerability affecting QEMU.

How does CVE-2017-5525 impact the system?

CVE-2017-5525 can lead to host memory consumption and crashes of the QEMU process due to memory leaks.

What versions of QEMU are affected by CVE-2017-5525?

CVE-2017-5525 affects QEMU versions prior to 2.8.1.1.

How can I mitigate the effects of CVE-2017-5525?

To mitigate CVE-2017-5525, upgrading to QEMU version 2.8.1.1 or later is recommended.

Who is affected by CVE-2017-5525?

Local guest OS privileged users can exploit CVE-2017-5525 on systems running susceptible versions of QEMU.

Vulnerability/
CVE-2017-5525

medium

6.5

CWE

401

15/3/2017

12/2/2023

CVE-2017-5525

First published: Wed Mar 15 2017(Updated: )

Memory leak in hw/audio/ac97.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.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
QEMU KVM	<=2.8.1.1
Debian Debian Linux	=8.0

Remedy

http://www.openwall.com/lists/oss-security/2017/01/17/19

Remedy

http://www.openwall.com/lists/oss-security/2017/01/18/7

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5525?
CVE-2017-5525 is classified as a denial of service vulnerability affecting QEMU.
How does CVE-2017-5525 impact the system?
CVE-2017-5525 can lead to host memory consumption and crashes of the QEMU process due to memory leaks.
What versions of QEMU are affected by CVE-2017-5525?
CVE-2017-5525 affects QEMU versions prior to 2.8.1.1.
How can I mitigate the effects of CVE-2017-5525?
To mitigate CVE-2017-5525, upgrading to QEMU version 2.8.1.1 or later is recommended.
Who is affected by CVE-2017-5525?
Local guest OS privileged users can exploit CVE-2017-5525 on systems running susceptible versions of QEMU.

agent/severity
agent/references
agent/weakness
agent/author
agent/description
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
agent/type
agent/tags
agent/remedy
agent/event
collector/nvd-index
agent/software-canonical-lookup-request
vendor/qemu
canonical/qemu kvm
version/qemu kvm/2.8.1.1
vendor/debian
canonical/debian debian linux
version/debian debian linux/8.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-5525?
CVE-2017-5525 is classified as a denial of service vulnerability affecting QEMU.
How does CVE-2017-5525 impact the system?
CVE-2017-5525 can lead to host memory consumption and crashes of the QEMU process due to memory leaks.
What versions of QEMU are affected by CVE-2017-5525?
CVE-2017-5525 affects QEMU versions prior to 2.8.1.1.
How can I mitigate the effects of CVE-2017-5525?
To mitigate CVE-2017-5525, upgrading to QEMU version 2.8.1.1 or later is recommended.
Who is affected by CVE-2017-5525?
Local guest OS privileged users can exploit CVE-2017-5525 on systems running susceptible versions of QEMU.