What is the severity of CVE-2016-9913?

The severity of CVE-2016-9913 is considered moderate due to the potential for local denial of service.

How do I fix CVE-2016-9913?

To fix CVE-2016-9913, upgrade QEMU to version 2.8.0-rc2 or later, as the vulnerability has been addressed in subsequent releases.

Which versions of QEMU are affected by CVE-2016-9913?

CVE-2016-9913 affects QEMU versions up to and including 2.7.1 and specific 2.8.0 release candidates.

What impact does CVE-2016-9913 have on system performance?

CVE-2016-9913 can cause significant memory consumption leading to a potential crash of the QEMU process.

Who can exploit CVE-2016-9913?

CVE-2016-9913 can be exploited by local privileged users within the guest operating system.

Vulnerability/
CVE-2016-9913

medium

6.5

CWE

401

29/12/2016

6/8/2024

CVE-2016-9913

First published: Thu Dec 29 2016(Updated: )

Memory leak in the v9fs_device_unrealize_common function in hw/9pfs/9p.c in QEMU (aka Quick Emulator) allows local privileged guest OS users to cause a denial of service (host memory consumption and possibly QEMU process crash) via vectors involving the order of resource cleanup.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
QEMU KVM	<=2.7.1
QEMU KVM	=2.8.0-rc0
QEMU KVM	=2.8.0-rc1

Remedy

https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg03278.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9913?
The severity of CVE-2016-9913 is considered moderate due to the potential for local denial of service.
How do I fix CVE-2016-9913?
To fix CVE-2016-9913, upgrade QEMU to version 2.8.0-rc2 or later, as the vulnerability has been addressed in subsequent releases.
Which versions of QEMU are affected by CVE-2016-9913?
CVE-2016-9913 affects QEMU versions up to and including 2.7.1 and specific 2.8.0 release candidates.
What impact does CVE-2016-9913 have on system performance?
CVE-2016-9913 can cause significant memory consumption leading to a potential crash of the QEMU process.
Who can exploit CVE-2016-9913?
CVE-2016-9913 can be exploited by local privileged users within the guest operating system.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/remedy
agent/author
agent/last-modified-date
agent/severity
agent/weakness
agent/event
agent/description
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/qemu
canonical/qemu kvm
version/qemu kvm/2.7.1
version/qemu kvm/2.8.0-rc0
version/qemu kvm/2.8.0-rc1

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-2016-9913?
The severity of CVE-2016-9913 is considered moderate due to the potential for local denial of service.
How do I fix CVE-2016-9913?
To fix CVE-2016-9913, upgrade QEMU to version 2.8.0-rc2 or later, as the vulnerability has been addressed in subsequent releases.
Which versions of QEMU are affected by CVE-2016-9913?
CVE-2016-9913 affects QEMU versions up to and including 2.7.1 and specific 2.8.0 release candidates.
What impact does CVE-2016-9913 have on system performance?
CVE-2016-9913 can cause significant memory consumption leading to a potential crash of the QEMU process.
Who can exploit CVE-2016-9913?
CVE-2016-9913 can be exploited by local privileged users within the guest operating system.