CVE-2024-8354: Qemu-kvm: usb: assertion failure in usb_ep_get()

Published Sep 19, 2024
·
Updated

A flaw was found in QEMU. An assertion failure was present in the usbepget() function in hw/net/core.c when trying to get the USB endpoint from a USB device. This flaw may allow a malicious unprivileged guest user to crash the QEMU process on the host and cause a denial of service condition.

Other sources

An assertion failure was found in QEMU in the usbepget() function in hw/net/core.c. The TD PID needs to be either USBTOKENIN or USBTOKENOUT in usbepget, but in the caller uhcihandletd it may be USBTOKENSETUP.

An unprivileged guest user may be able to reach the assertion. Users are not directly able to craft URBs, however as a user, one might be able to find a kernel path that would send a TD with PID USBTOKENSETUP to QEMU (which is called USBPIDSETUP in Linux). For instance in the Linux Kernel, uhcisubmitcontrol in drivers/usb/host/uhci-q.c:789 does link a USBPIDSETUP TD to the URB.

Upstream issue: https://gitlab.com/qemu-project/qemu/-/issues/2548

Red Hat

Qemu-kvm: usb: assertion failure in usbepget()

Microsoft

Affected Software

14 affected componentsFixes available
Qemu Qemu
redhat Enterprise Linux=6.0
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
Microsoft azl3 qemu 8.2.0-23
Microsoft cbl2 qemu 6.2.0-27<6.2.0-27
6.2.0-27
Microsoft azl3 qemu 9.1.0-3<9.1.0-3
9.1.0-3
Microsoft cbl2 qemu 6.2.0-25
Microsoft cbl2 qemu 6.2.0-24
Microsoft cbl2 qemu 6.2.0-26<6.2.0-27
6.2.0-27
Microsoft azl3 qemu 8.2.0-19
Microsoft azl3 qemu 8.2.0-17

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.0-27
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.1.0-3

Event History

Sep 19, 2024
Data Sourced
via Red Hat·09:19 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·10:45 AM
Data Sourced
via MITRE·10:45 AM
DescriptionSeverityWeakness
Sep 4, 2025
Data Sourced
via Microsoft·03:32 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·03:32 AM
Affected Software
Updated
via Microsoft·03:32 AM
SeverityAffected Software
Updated
via Microsoft·10:32 AM
DescriptionSeverity
Updated
via Microsoft·10:32 AM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-8354?

CVE-2024-8354 is classified with a severity level that indicates potential denial of service risks for QEMU users.

2

How do I fix CVE-2024-8354?

To fix CVE-2024-8354, users should update QEMU to the latest version that includes patches for this vulnerability.

3

What impact does CVE-2024-8354 have on affected systems?

CVE-2024-8354 may allow unprivileged guest users to crash the QEMU process, leading to a denial of service.

4

Which versions of QEMU are affected by CVE-2024-8354?

CVE-2024-8354 affects multiple versions of QEMU across various distributions, including those running on Red Hat Enterprise Linux.

5

Is CVE-2024-8354 exploitable remotely?

CVE-2024-8354 is considered a denial of service vulnerability that could be exploited locally by unprivileged guest users.

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