What is the severity of CVE-2016-9102?

CVE-2016-9102 is considered a moderate severity vulnerability due to the potential for denial of service.

How do I fix CVE-2016-9102?

To fix CVE-2016-9102, upgrade to a version of QEMU later than 2.7.1 where this vulnerability has been addressed.

Who is affected by CVE-2016-9102?

CVE-2016-9102 affects local guest OS administrators using vulnerable versions of QEMU and Debian 8.0.

What does CVE-2016-9102 exploit?

CVE-2016-9102 exploits a memory leak in the v9fs_xattrcreate function, leading to high memory consumption.

What can be the impact of CVE-2016-9102?

The impact of CVE-2016-9102 can result in a denial of service, causing the QEMU process to crash.

Vulnerability/
CVE-2016-9102

medium

CWE

772

9/12/2016

6/8/2024

CVE-2016-9102

First published: Fri Dec 09 2016(Updated: )

Memory leak in the v9fs_xattrcreate function in hw/9pfs/9p.c in QEMU (aka Quick Emulator) allows local guest OS administrators to cause a denial of service (memory consumption and QEMU process crash) via a large number of Txattrcreate messages with the same fid number.

Credit: secalert@redhat.com

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

Remedy

https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg01861.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9102?
CVE-2016-9102 is considered a moderate severity vulnerability due to the potential for denial of service.
How do I fix CVE-2016-9102?
To fix CVE-2016-9102, upgrade to a version of QEMU later than 2.7.1 where this vulnerability has been addressed.
Who is affected by CVE-2016-9102?
CVE-2016-9102 affects local guest OS administrators using vulnerable versions of QEMU and Debian 8.0.
What does CVE-2016-9102 exploit?
CVE-2016-9102 exploits a memory leak in the v9fs_xattrcreate function, leading to high memory consumption.
What can be the impact of CVE-2016-9102?
The impact of CVE-2016-9102 can result in a denial of service, causing the QEMU process to crash.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/severity
agent/remedy
agent/references
agent/weakness
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
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-2016-9102?
CVE-2016-9102 is considered a moderate severity vulnerability due to the potential for denial of service.
How do I fix CVE-2016-9102?
To fix CVE-2016-9102, upgrade to a version of QEMU later than 2.7.1 where this vulnerability has been addressed.
Who is affected by CVE-2016-9102?
CVE-2016-9102 affects local guest OS administrators using vulnerable versions of QEMU and Debian 8.0.
What does CVE-2016-9102 exploit?
CVE-2016-9102 exploits a memory leak in the v9fs_xattrcreate function, leading to high memory consumption.
What can be the impact of CVE-2016-9102?
The impact of CVE-2016-9102 can result in a denial of service, causing the QEMU process to crash.