Opened 3 years ago
Last modified 3 years ago
#20385 new defect
VirtualBox crashes by accessing 0xFFFFFFFFFFFFFFFF when USB dongle is unplugged/plugged.
| Reported by: | ci-zephyurus | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.22 |
| Keywords: | USB crash | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
I am using virtualbox 6.1.22: 6.1.22 r144080 (Qt5.6.2) to be exact. Host is Windows 10 Pro 64-bit., 20H2, OS build is 19042.985 Guest is Debian GNU/Linux, 5.10.0-4-amd64
I have a USB Wi-Fi dongle NEC Aterm WL300NU-AG adaptor. This works fine under Windows 10.
I tried to use this dongle from within linux to test my Wi-Fi devices at home against fragattacks (recently found Wi-Fi vulnerability). So I removed the driver under Windows 10 for this USB. (It is plugged and no messing from Windoes 10 itself without the driver, I suppose.) I intend to use the dongle via the native linux driver.
Under guest linux, I could somehow make the dongle recognized initially, and eventually was able to assign IP address to it (manually, not by DHCP) and ping the interface address from other PCs via Wi-Fi. So experimentally it works, but the device went off-line unexpectedly. The driver seems to have a known issue. In order to reset the device, I tried unplugging and plugging it a few times. Then VBox crashed saying it accessed 0xFFFFFFFFFFFFFFFF address. (Actually I did this a lot initially, but at that time VBox did not crash.)
Alright, I saved a log. (The experiment took a couple of hours).
Now, I rebooted the guest linux by restarting VBox and see if I can continue testing the dongle. Nope. The device was not visible from within guest linux using lsusb anymore(?!). So I tried unplugging and unplugging only a couple of times when I get the same address violation and VBox crashed. This time I got the capture on the screen to show the address.
I think there is a problem with USB handling. I am attaching the first log (crash that occurred after a couple of hours testing. Actually, it was at the tail end of a very long session.) and the second log along with the screen dump.
Attachments (3)
Change History (4)
by , 3 years ago
| Attachment: | debian64bit-Rev02-2021-06-03-12-53-31.log added |
|---|
by , 3 years ago
| Attachment: | vbox-crash.PNG added |
|---|
The screen dialog that appeared when VBox crashed the second time
by , 3 years ago
| Attachment: | debian64bit-Rev02-2021-06-03-13-10-27.log added |
|---|
Log of VBox crashing the second time.
comment:1 by , 3 years ago
The screen dialog DID appear at the first crash, but I failed to capture it.
The screen dialog I attached says, the instruction at 0x00007F ... 47 accessed address 0xFFFFFFFFFFFFFFFF. It could not be read in Japanese.
Log of VBox crashing the first time (when USB dongle was unplugged/plugged)