What is the severity of CVE-2016-9912?

CVE-2016-9912 is classified as a moderate severity vulnerability due to the potential for memory leakage that can lead to denial of service.

How do I fix CVE-2016-9912?

To fix CVE-2016-9912, upgrade QEMU to a version later than 2.8.1.1 that addresses the memory leakage issue.

Who is affected by CVE-2016-9912?

Users running QEMU versions up to and including 2.8.1.1 with Virtio GPU Device emulator support are affected by CVE-2016-9912.

What type of issue is CVE-2016-9912?

CVE-2016-9912 is a memory leakage issue that occurs when destroying GPU resource objects in QEMU.

Can CVE-2016-9912 cause a denial of service?

Yes, a guest user or process exploiting CVE-2016-9912 can leak host memory bytes, resulting in potential denial of service for the host.

Vulnerability/
CVE-2016-9912

medium

6.5

CWE

772

23/12/2016

6/8/2024

CVE-2016-9912

First published: Fri Dec 23 2016(Updated: )

Quick Emulator (Qemu) built with the Virtio GPU Device emulator support is vulnerable to a memory leakage issue. It could occur while destroying gpu resource object in 'virtio_gpu_resource_destroy'. A guest user/process could use this flaw to leak host memory bytes, resulting in DoS for a host.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
QEMU KVM	<=2.8.1.1

Remedy

http://www.openwall.com/lists/oss-security/2016/12/08/6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9912?
CVE-2016-9912 is classified as a moderate severity vulnerability due to the potential for memory leakage that can lead to denial of service.
How do I fix CVE-2016-9912?
To fix CVE-2016-9912, upgrade QEMU to a version later than 2.8.1.1 that addresses the memory leakage issue.
Who is affected by CVE-2016-9912?
Users running QEMU versions up to and including 2.8.1.1 with Virtio GPU Device emulator support are affected by CVE-2016-9912.
What type of issue is CVE-2016-9912?
CVE-2016-9912 is a memory leakage issue that occurs when destroying GPU resource objects in QEMU.
Can CVE-2016-9912 cause a denial of service?
Yes, a guest user or process exploiting CVE-2016-9912 can leak host memory bytes, resulting in potential denial of service for the host.

agent/type
collector/mitre-cve
source/MITRE
agent/remedy
agent/author
agent/last-modified-date
agent/severity
agent/weakness
agent/references
agent/softwarecombine
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.8.1.1

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-9912?
CVE-2016-9912 is classified as a moderate severity vulnerability due to the potential for memory leakage that can lead to denial of service.
How do I fix CVE-2016-9912?
To fix CVE-2016-9912, upgrade QEMU to a version later than 2.8.1.1 that addresses the memory leakage issue.
Who is affected by CVE-2016-9912?
Users running QEMU versions up to and including 2.8.1.1 with Virtio GPU Device emulator support are affected by CVE-2016-9912.
What type of issue is CVE-2016-9912?
CVE-2016-9912 is a memory leakage issue that occurs when destroying GPU resource objects in QEMU.
Can CVE-2016-9912 cause a denial of service?
Yes, a guest user or process exploiting CVE-2016-9912 can leak host memory bytes, resulting in potential denial of service for the host.