KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ eff484e0298da5a4d18ca82f5454c557fd942af5 · < 3d4c26b16a04a084fe0bde08ccdd8086570f8bbe| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save
MAPC with V=0 drops ite->collection but leaves the ITE on the device's ITT list, and vgic_its_save_ite() dereferences it unconditionally. A guest that issues MAPD, MAPTI and then MAPC(V=0) therefore oopses the host when the VMM issues KVM_DEV_ARM_ITS_SAVE_TABLES to migrate it. That sequence is UNPREDICTABLE per the architecture, but KVM already handles the resulting state in the translate, MOVI and DISCARD paths.
Save a zeroed entry, which vgic_its_restore_ite() reads back as invalid. Skipping the ITE instead would leave the ITT slot holding whatever is in guest memory, and restore rejects an entry naming a collection the restored collection table does not have.
From the CVE record · Linux
The Linux kernel's KVM arm64 interrupt controller can dereference a NULL collection while saving an interrupt translation table entry. A guest can trigger a host crash by issuing MAPD, MAPTI and MAPC(V=0), if the VMM subsequently saves the ITS tables for migration.
Operators running Linux hosts with KVM arm64 guests should check their kernel versions; affected versions are not specified.