KVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: vgic: Avoid double-deactivate of IRQs in the nested context
In the nested state, the physical interrupt has already been deactivated through the HW bit in the LR. The extra deactivation would be harmless but can hit an errata case on AmpereOne, so avoid it here.
On AmpereOne, deactivating a physical interrupt through ICC_DIR_EL1 or ICC_EOIR1_EL1 (depending on EOImode) which is not active, but is the highest priority pending interrupt causes the cpu to lose the interrupt pending state and also prevents the delivery of future interrupts.
From the CVE record · Linux
The Linux kernel’s KVM arm64 vgic can deactivate an interrupt twice in a nested context. On AmpereOne, this can lose the interrupt’s pending state and prevent future interrupts from being delivered. The input does not describe an attacker or the access needed to trigger this condition.
Engineers running Linux with KVM arm64 nested virtualization on AmpereOne should check their kernel; affected versions are not specified.