Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-6505

Qemu: usb: an infinite loop issue in ohci_service_ed_list

Overview

Published
15 Mar 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
9 OS packages
4 Linux distributions
Yes Fix available

Description

The ohci_service_ed_list function in hw/usb/hcd-ohci.c in QEMU (aka Quick Emulator) before 2.9.0 allows local guest OS users to cause a denial of service (infinite loop) via vectors involving the number of link endpoint list descriptors, a different vulnerability than CVE-2017-9330.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

Weakness: CWE-835

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 10 fixes

debian 4 releases · 1 package

fixed 4
qemu
debian fixes for CVE-2017-6505
ReleasePackageFixed in
11 qemu 1:2.8+dfsg-4
12 qemu 1:2.8+dfsg-4
13 qemu 1:2.8+dfsg-4
14 qemu 1:2.8+dfsg-4

echo 1 release · 1 package

fixed 1
qemu
echo fixes for CVE-2017-6505
ReleasePackageFixed in
qemu 1:2.8+dfsg-4

openSUSE 1 release · 1 package

fixed 1
xen
openSUSE fixes for CVE-2017-6505
ReleasePackageFixed inAdvisory
Tumbleweed xen +7 4.15.1_01-1.2 openSUSE-SU-2024:11520-1

ubuntu 4 releases · 1 package

fixed 4
qemu
ubuntu fixes for CVE-2017-6505
ReleasePackageFixed in
18.04 qemu 1:2.8+dfsg-3ubuntu2.1
18.04-ESM qemu 1:2.8+dfsg-3ubuntu2.1
20.04 qemu 1:2.8+dfsg-3ubuntu2.1
20.04-ESM qemu 1:2.8+dfsg-3ubuntu2.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.