I seem to have been able to fix it. Enabling Intel Virtualisation Technology in the host machine's BIOS settings seems to have resolved the issue. Not sure why that was off in the first place, but there you go.
According to the bug report, this issue has been resolved in the VirtualBox SVN, and will be included in the next 4.3.x maintenance release.