VirtualBox 7.2.18 adds support for Linux kernel 7.3 and RHEL 10.3, and fixes 3D crashes, VDI corruption, and Windows 11 ARM issues.

The VDI fix is the one that matters

VDI is VirtualBox’s native disk image format. A corruption bug in it means guest data at risk, which places this above the usual point release in importance.

If you run VirtualBox with VDI images, update, and then do the thing nobody does: verify a backup of anything you care about actually restores. Our backup guide covers that, and a disk-image corruption bug is exactly the scenario where people discover their VM backups were never tested.

Kernel 7.3 support, ahead of the kernel

Worth understanding if you have ever had VirtualBox break after a system update.

VirtualBox needs kernel modules, and those modules use internal kernel interfaces that carry no stability guarantee. When the kernel changes them, the modules fail to build, and VirtualBox stops working until Oracle ships a release that accommodates the change.

Shipping 7.3 support now, with 7.3 still in release candidates and due in late October, means the modules will build when the kernel arrives rather than a few weeks later. That gap is the recurring VirtualBox complaint, and getting ahead of it is the right call.

# after a kernel update, the modules rebuild via DKMS
dkms status | grep vbox
sudo /sbin/vboxconfig

Our DKMS explainer covers the rebuild mechanism, and it is the thing to check first when VirtualBox stops working after an upgrade.

VirtualBox against KVM on Linux

The comparison worth making, since on Linux you have a better option built in.

KVM is in the kernel. No out-of-tree modules, nothing to rebuild after an upgrade, and near-native performance because the hypervisor is part of the operating system rather than layered on it. Our KVM and QEMU guide and the virt-manager guide cover it, and GPU passthrough is possible in a way VirtualBox does not match.

VirtualBox is cross-platform, has a friendlier interface, and its snapshot and appliance handling is genuinely convenient. If you move VMs between Linux, macOS, and Windows, or you want something that works the same everywhere, it earns its place.

For a Linux-only workflow, KVM is the better technical choice and avoids this entire category of module-breakage problem. For anything portable, VirtualBox remains the pragmatic answer.

This follows 7.2.16, which added Linux FRED support and improved Wayland clipboard handling.