What is the severity of CVE-2016-9846?

CVE-2016-9846 is classified as a high severity vulnerability due to its potential to cause denial of service (DoS) on the host.

How does CVE-2016-9846 affect QEMU?

CVE-2016-9846 allows a guest user/process to leak host memory bytes during cursor data updates, leading to possible service disruption.

What versions of QEMU are affected by CVE-2016-9846?

QEMU versions up to 2.7.1 and specifically 2.8.0-rc0, 2.8.0-rc1, and 2.8.0-rc2 are affected by CVE-2016-9846.

How do I fix CVE-2016-9846?

To mitigate CVE-2016-9846, users should upgrade to a version of QEMU that is beyond the affected versions, specifically after 2.8.0-rc2.

Is there a workaround for CVE-2016-9846?

Currently, there are no effective workarounds for CVE-2016-9846 other than applying the recommended updates.

Vulnerability/
CVE-2016-9846

medium

6.5

CWE

119

29/12/2016

6/8/2024

CVE-2016-9846: Buffer Overflow

First published: Thu Dec 29 2016(Updated: )

QEMU (aka Quick Emulator) built with the Virtio GPU Device emulator support is vulnerable to a memory leakage issue. It could occur while updating the cursor data in update_cursor_data_virgl. 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.7.1
QEMU KVM	=2.8.0-rc0
QEMU KVM	=2.8.0-rc1
QEMU KVM	=2.8.0-rc2

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9846?
CVE-2016-9846 is classified as a high severity vulnerability due to its potential to cause denial of service (DoS) on the host.
How does CVE-2016-9846 affect QEMU?
CVE-2016-9846 allows a guest user/process to leak host memory bytes during cursor data updates, leading to possible service disruption.
What versions of QEMU are affected by CVE-2016-9846?
QEMU versions up to 2.7.1 and specifically 2.8.0-rc0, 2.8.0-rc1, and 2.8.0-rc2 are affected by CVE-2016-9846.
How do I fix CVE-2016-9846?
To mitigate CVE-2016-9846, users should upgrade to a version of QEMU that is beyond the affected versions, specifically after 2.8.0-rc2.
Is there a workaround for CVE-2016-9846?
Currently, there are no effective workarounds for CVE-2016-9846 other than applying the recommended updates.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/remedy
agent/weakness
agent/severity
agent/last-modified-date
agent/author
agent/first-publish-date
agent/event
agent/description
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
version/qemu kvm/2.8.0-rc2

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-9846?
CVE-2016-9846 is classified as a high severity vulnerability due to its potential to cause denial of service (DoS) on the host.
How does CVE-2016-9846 affect QEMU?
CVE-2016-9846 allows a guest user/process to leak host memory bytes during cursor data updates, leading to possible service disruption.
What versions of QEMU are affected by CVE-2016-9846?
QEMU versions up to 2.7.1 and specifically 2.8.0-rc0, 2.8.0-rc1, and 2.8.0-rc2 are affected by CVE-2016-9846.
How do I fix CVE-2016-9846?
To mitigate CVE-2016-9846, users should upgrade to a version of QEMU that is beyond the affected versions, specifically after 2.8.0-rc2.
Is there a workaround for CVE-2016-9846?
Currently, there are no effective workarounds for CVE-2016-9846 other than applying the recommended updates.