KVM: Stop looking for coalesced MMIO zones if the bus is destroyed
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
f0dfffce3f4ffd5f822568a4a6fb34c010e939d1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: Stop looking for coalesced MMIO zones if the bus is destroyed
Abort the walk of coalesced MMIO zones if kvm_io_bus_unregister_dev() fails to allocate memory for the new instance of the bus. If it can't instantiate a new bus, unregister_dev() destroys all devices _except_ the target device. But, it doesn't tell the caller that it obliterated the bus and invoked the destructor for all devices that were on the bus. In the coalesced MMIO case, this can result in a deleted list entry dereference due to attempting to continue iterating on coalesced_zones after future entries (in the walk) have been deleted.
Opportunistically add curly braces to the for-loop, which encompasses many lines but sneaks by without braces due to the guts being a single if statement.
From the CVE record · Linux
The Linux kernel's KVM coalesced MMIO handling can dereference a deleted list entry if unregistering a device fails to allocate memory and destroys the bus during a zone walk. This can cause a crash; the input does not specify attacker access, authentication requirements, or user interaction.
Engineers running the Linux kernel with KVM should check their deployments; affected versions are not specified.