Comment # 8 on bug 1202851 from Larry Rainey

Is the USB 3.2 drive available in Linux after the shutdown/reboot or is it in
limbo. If it is in limbo - you may have found a Kernel flaw - the kernel may
not see that as a disk and is not returning it to the available USB pool of
devices. If it is still "attached" to the virtual machine instead of the host.
Virtualbox is trying to reconnect to a limbo drive and forced to abort the
virtual machine. Now that the Virtual Machine has aborted the limbo drive is
back to Linux and can be assigned again.

This is my guess as to why - I am trying to guess as to why - I know that when
USB 3 came out - many issues with devices happened in the kernel. 12 years have
passed but USB 3 is still evolving and it is possible that some of the new
thunderbolt code has issues knowing the device categories correctly. I suspect
that your drive is plugged into a unit that has thunderbolt USB port(s).

My 2 cents. - YMMV