What is the severity of CVE-2016-6834?

CVE-2016-6834 has a severity rating that indicates it can lead to a denial of service condition.

How do I fix CVE-2016-6834?

To mitigate CVE-2016-6834, you should upgrade QEMU to the latest version or apply any available patches.

What versions are affected by CVE-2016-6834?

CVE-2016-6834 affects QEMU versions up to 2.6.2 and specific release candidates of version 2.7.0.

What is the impact of CVE-2016-6834?

The impact of CVE-2016-6834 is that it can cause an infinite loop and crash the QEMU process.

Who is vulnerable to CVE-2016-6834?

Local guest OS administrators using vulnerable versions of QEMU are susceptible to CVE-2016-6834.

Vulnerability/
CVE-2016-6834

medium

4.4

CWE

120

10/12/2016

6/8/2024

CVE-2016-6834

First published: Sat Dec 10 2016(Updated: )

The net_tx_pkt_do_sw_fragmentation function in hw/net/net_tx_pkt.c in QEMU (aka Quick Emulator) allows local guest OS administrators to cause a denial of service (infinite loop and QEMU process crash) via a zero length for the current fragment length.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
QEMU KVM	<=2.6.2
QEMU KVM	=2.7.0-rc0
QEMU KVM	=2.7.0-rc1
QEMU KVM	=2.7.0-rc2
Debian Debian Linux	=8.0

Remedy

https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg01601.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6834?
CVE-2016-6834 has a severity rating that indicates it can lead to a denial of service condition.
How do I fix CVE-2016-6834?
To mitigate CVE-2016-6834, you should upgrade QEMU to the latest version or apply any available patches.
What versions are affected by CVE-2016-6834?
CVE-2016-6834 affects QEMU versions up to 2.6.2 and specific release candidates of version 2.7.0.
What is the impact of CVE-2016-6834?
The impact of CVE-2016-6834 is that it can cause an infinite loop and crash the QEMU process.
Who is vulnerable to CVE-2016-6834?
Local guest OS administrators using vulnerable versions of QEMU are susceptible to CVE-2016-6834.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/references
agent/severity
agent/remedy
agent/weakness
agent/description
agent/event
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.6.2
version/qemu kvm/2.7.0-rc0
version/qemu kvm/2.7.0-rc1
version/qemu kvm/2.7.0-rc2
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-6834?
CVE-2016-6834 has a severity rating that indicates it can lead to a denial of service condition.
How do I fix CVE-2016-6834?
To mitigate CVE-2016-6834, you should upgrade QEMU to the latest version or apply any available patches.
What versions are affected by CVE-2016-6834?
CVE-2016-6834 affects QEMU versions up to 2.6.2 and specific release candidates of version 2.7.0.
What is the impact of CVE-2016-6834?
The impact of CVE-2016-6834 is that it can cause an infinite loop and crash the QEMU process.
Who is vulnerable to CVE-2016-6834?
Local guest OS administrators using vulnerable versions of QEMU are susceptible to CVE-2016-6834.