Vulnerabilities

Vulnerability · CVE-2026-72289

KVM: arm64: vgic: Check the interrupt is still ours before migrating it

Published Aug 15, 2026 · catalog updated Oct 13, 2026 · KVM: arm64: vgic: Check

Check if you run it

No confirmed exploitation is on record for CVE-2026-72289. EPSS is 0.18%. Act only if a listed version of KVM: arm64: vgic: Check is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (KVM: arm64: vgic: Check).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.18%
Remediation
Not established
Affected products
Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Check the interrupt is still ours before migrating it vgic_prune_ap_list() drops both ap_list_lock and irq_lock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity is unchanged (target_vcpu == vgic_target_oracle(irq)) before moving the interrupt, which assumes that an interrupt whose affinity is preserved is still queued on this vCPU's ap_list. That assumption no longer holds if the interrupt is taken off the ap_list while the locks are dropped. vgic_flush_pending_lpis() removes the interrupt from the list and sets irq->vcpu to NULL, but leaves enabled/pending/target_vcpu untouched. As the interrupt is still enabled and pending, vgic_target_oracle() returns the same target_vcpu, so the affinity check passes and list_del() is run a second time on an entry that has already been removed. Also check that the interrupt is still assigned to this vCPU (irq->vcpu == vcpu) before moving it.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Linux Kernel4.7.0 → 5.10.261

How to fix CVE-2026-72289

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-72289. EPSS is 0.18%. Act only if a listed version of KVM: arm64: vgic: Check is installed.

Which versions are affected?

Compare what you have installed with Kernel 4.7.0 → 5.10.261. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.18%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 15, 2026 · Catalog

    Detected

    In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Check the interrupt is still ours before migrating it vgic_prune_ap_list() drops both ap_list_lock and irq_lock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity is unchanged (target_vcpu == vgic_target_oracle(irq)) before moving the interrupt, which assume

  2. Oct 13, 2026 · Catalog

    Fix available

    Linux Kernel 4.7.0 → 5.10.261

  3. Oct 13, 2026 · Catalog

    Updated

    In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: vgic: Check the interrupt is still ours before migrating it vgic_prune_ap_list() drops both ap_list_lock and irq_lock while migrating an interrupt to another vCPU. After reacquiring the locks it only checks that the affinity is unchanged (target_vcpu == vgic_target_oracle(irq)) before moving the interrupt, which assume

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.