CVE-2016-4037
Public on
Last Modified:
Description
The CVE Program describes this issue as:
The ehci_advance_state function in hw/usb/hcd-ehci.c in QEMU allows local guest OS administrators to cause a denial of service (infinite loop and CPU consumption) via a circular split isochronous transfer descriptor (siTD) list, a related issue to CVE-2015-8558.
Statement
This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.
Additional information
- Bugzilla 1325129: Qemu: usb: Infinite loop vulnerability in usb_ehci using siTD process
- CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
- FAQ: Frequently asked questions about CVE-2016-4037
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
| Red Hat | NVD | |
|---|---|---|
CVSS v2 Base Score | 2.3 | 4.9 |
Attack Vector | Adjacent Network | Local |
Access Complexity | Medium | Low |
Authentication | Single | None |
Confidentiality Impact | None | None |
Integrity Impact | None | None |
Availability Impact | Partial | Complete |
CVSS v2 Vector
Red Hat: AV:A/AC:M/Au:S/C:N/I:N/A:P
NVD: AV:L/AC:L/Au:N/C:N/I:N/A:C
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Amplification
An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.
Acknowledgements
Red Hat would like to thank Du Shaobo (Qihoo 360) for reporting this issue.
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
What can I do if my product is listed as "Will not fix"?
What can I do if my product is listed as "Fix deferred"?
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
