KVM: x86: Reset IRTE to host control if *new* route isn't postable
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ efc644048ecde54f016011fe10110addd0de348f · < 3066ec21d1a33896125747f68638725f456308db| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: x86: Reset IRTE to host control if *new* route isn't postable
Restore an IRTE back to host control (remapped or posted MSI mode) if the *new* GSI route prevents posting the IRQ directly to a vCPU, regardless of the GSI routing type. Updating the IRTE if and only if the new GSI is an MSI results in KVM leaving an IRTE posting to a vCPU.
The dangling IRTE can result in interrupts being incorrectly delivered to the guest, and in the worst case scenario can result in use-after-free, e.g. if the VM is torn down, but the underlying host IRQ isn't freed.
From the CVE record · Linux
A KVM x86 routing update can leave an interrupt remapping table entry (IRTE) posting interrupts to a vCPU when the new route no longer permits it. This can misdeliver interrupts to a guest and may cause a use-after-free if the VM is torn down while the underlying host IRQ remains allocated; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernel KVM on x86 should check their installations; affected versions are not specified.