Seems like the issue has been fixed in VirtualBox 5.2.22

https://github.com/MorteNoir1/virtualbox_e1000_0day/issues/1... https://www.virtualbox.org/wiki/Changelog#22