CVE-2026-99573: KVM: arm64: vgic: Stop the target vcpu when disabling LPIs

Published Nov 20, 2026
·
Updated

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

7 affected componentsFixes available
linux/kernel>=5.1.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:49 AM
Data Sourced
via MITRE·05:49 AM
Description
Data Sourced
via OSV·05:49 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

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.

2

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.

3

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203