CVE-2026-99573: KVM: arm64: vgic: Stop the target vcpu when disabling LPIs
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: vgic: Stop the target vcpu when disabling LPIs
Disabling LPIs is pretty nasty, as it directly messes with the AP list of the affected CPU, which could be running... This has the potential to lead to really bad behaviours, and we should not be doing that.
Take example on the way the Active state is handled and simply pause the the vcpu so that we are sure it is in a quiescent state, and the state be safely manipulated.
Nobody has any expectation of performance for this anyway.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
The issue applies to Linux kernel systems using KVM on arm64 with the virtual GIC (vgic) and Locality-specific Peripheral Interrupts (LPIs). Systems not using this KVM arm64 virtualization path are not indicated as affected by the provided information.
What condition triggers the unsafe behavior?
The condition occurs when LPIs are disabled for an affected CPU while its target vCPU could still be running. Disabling LPIs directly modifies that CPU's active-pending list, so doing so without first quiescing the vCPU can lead to unsafe behavior.
What does the fix change?
The fix pauses the target vCPU before disabling LPIs, ensuring that the vCPU is quiescent while its state is manipulated. This avoids modifying the affected CPU's active-pending list while it may be executing.