RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

https://github.com/daynix/UsbDk/issues/59

This issue was originally reported here:

The reported post:
A BSoD occurred when I plugged in a huawei phone. It's about an 80 percent probability that happened.
Log attached below.
UsbDkTrace.zip
I traced the code and it seemed that phone was recognized as a hub due to an error when requesting the phone's Device descriptor.
Any help will be greatly appreciated!

Created attachment 1432404 [details]
UsbDkTrace_blueescreen.etl parsed to text

Thanks for filing the bug here too. Added to 4.3.

There is no simple way to reproduce the problem: it can be reproduced on Windows 7 (on Win10 it does not happen or reproduction rate is very low), for that needed composite USB device that contains at least 2 interfaces when one of them is CD.
Not having such device, I've succeeded to simulate it with spice-gtk pilot supporting cd-sharing (https://gitlab.freedesktop.org/yuri_benditovich/spice-gtk/tree/cd-sharing-as-composite), modified to create composite device with additional interface. When such device shared with guest, crash happens 4/5.
The fix applied   
https://github.com/daynix/UsbDk/commit/960f44ed2c697178235caa088a04ac38bd8e675c

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

4.3.1 has been released, please re-target this bug as soon as possible.

4.3.1 has been released a while ago as RHV 4.3 Beta2.
Re-targeting to 4.3.3 for re-evaluation.

Fixed in 1.0.21
https://www.spice-space.org/download/windows/usbdk/UsbDk_1.0.21_x64.msi
https://www.spice-space.org/download/windows/usbdk/UsbDk_1.0.21_x86.msi