What is the severity of CVE-2016-7155?

CVE-2016-7155 is classified as a high severity vulnerability due to its ability to cause a denial of service.

How do I fix CVE-2016-7155?

To fix CVE-2016-7155, update QEMU to version 2.7.2 or later.

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

CVE-2016-7155 affects QEMU versions up to and including 2.7.1.

What impact does CVE-2016-7155 have on systems?

CVE-2016-7155 can lead to out-of-bounds access or an infinite loop, resulting in the crash of the QEMU process.

What types of systems are vulnerable to CVE-2016-7155?

Systems running vulnerable versions of QEMU, particularly on Debian Linux 8.0 and below, are susceptible to CVE-2016-7155.

Vulnerability/
CVE-2016-7155

medium

4.4

10/12/2016

6/8/2024

CVE-2016-7155

First published: Sat Dec 10 2016(Updated: )

hw/scsi/vmw_pvscsi.c in QEMU (aka Quick Emulator) allows local guest OS administrators to cause a denial of service (out-of-bounds access or infinite loop, and QEMU process crash) via a crafted page count for descriptor rings.

Credit: cve@mitre.org

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

Remedy

http://git.qemu.org/?p=qemu.git;a=commit;h=7f61f4690dd153be98900a2a508b88989e692753

Remedy

https://lists.gnu.org/archive/html/qemu-devel/2016-09/msg00050.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-7155?
CVE-2016-7155 is classified as a high severity vulnerability due to its ability to cause a denial of service.
How do I fix CVE-2016-7155?
To fix CVE-2016-7155, update QEMU to version 2.7.2 or later.
Which versions of QEMU are affected by CVE-2016-7155?
CVE-2016-7155 affects QEMU versions up to and including 2.7.1.
What impact does CVE-2016-7155 have on systems?
CVE-2016-7155 can lead to out-of-bounds access or an infinite loop, resulting in the crash of the QEMU process.
What types of systems are vulnerable to CVE-2016-7155?
Systems running vulnerable versions of QEMU, particularly on Debian Linux 8.0 and below, are susceptible to CVE-2016-7155.

agent/type
agent/remedy
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/references
agent/last-modified-date
agent/description
agent/first-publish-date
agent/softwarecombine
agent/event
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-7155?
CVE-2016-7155 is classified as a high severity vulnerability due to its ability to cause a denial of service.
How do I fix CVE-2016-7155?
To fix CVE-2016-7155, update QEMU to version 2.7.2 or later.
Which versions of QEMU are affected by CVE-2016-7155?
CVE-2016-7155 affects QEMU versions up to and including 2.7.1.
What impact does CVE-2016-7155 have on systems?
CVE-2016-7155 can lead to out-of-bounds access or an infinite loop, resulting in the crash of the QEMU process.
What types of systems are vulnerable to CVE-2016-7155?
Systems running vulnerable versions of QEMU, particularly on Debian Linux 8.0 and below, are susceptible to CVE-2016-7155.