CVE-2017-9374: Medium severity Qemu Qemu vulnerability

Published Jun 6, 2017
·
Updated

Last updated 24 July 2024

Other sources

Memory leak in QEMU (aka Quick Emulator), when built with USB EHCI Emulation support, allows local guest OS privileged users to cause a denial of service (memory consumption) by repeatedly hot-unplugging the device.

Launchpad

Quick Emulator(Qemu) built with the USB EHCI Emulation support is vulnerable to a memory leakage issue. It could occur while hotunplugging the device, as it does not release the memory allocated at initialisation.

A guest user/process could use this issue to leak host memory, resulting in DoS for host.

Upstream patch: --------------- -> http://git.qemu.org/?p=qemu.git;a=commit;h=d710e1e7bd3d5bfc26b631f02ae87901ebe646b0

Reference: ---------- -> http://www.openwall.com/lists/oss-security/2017/06/06/3

Red Hat

Affected Software

2 affected componentsFixes available
Qemu Qemu<=2.8.1.1
debian/qemu
1:5.2+dfsg-11+deb11u31:5.2+dfsg-11+deb11u21:7.2+dfsg-7+deb12u121:10.0.0~rc3+ds-2

Event History

Jun 6, 2017
Data Sourced
via Red Hat·11:57 AM
DescriptionSeverityAffected Software
Jun 16, 2017
CVE Published
via MITRE·10:00 PM
Data Sourced
via MITRE·10:00 PM
Description
Jan 11, 2024
Data Sourced
via Launchpad·10:42 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:19 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this issue?

The vulnerability ID for this issue is CVE-2017-9374.

2

What is the title of this vulnerability?

The title of this vulnerability is 'Memory leak in QEMU (aka Quick Emulator) when built with USB EHCI Emulation support allows local guest OS privileged users to cause a denial of service (memory consumption) by repeatedly hot-unplugging the device.'

3

What is the severity level of CVE-2017-9374?

The severity level of CVE-2017-9374 is low.

4

How does CVE-2017-9374 affect the software?

CVE-2017-9374 affects the software QEMU when built with USB EHCI Emulation support.

5

How can CVE-2017-9374 be fixed?

CVE-2017-9374 can be fixed by applying the recommended patches provided by the software vendor.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203