Strix
56.7K

CVE-2026-72289

CRITICALCVSS 9.3/10EPSS 0.21%

Last modified

CVE-2026-72289 is a critical-severity vulnerability rated 9.3/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1
9.3/10

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS Probability
0.21%

11.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < 3893e1fcf6f306b327a8358dcd1cbd077989a240; >= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < cb3efe1a354f1638726725c3ecee1ce8d1a7e2dc; >= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < da2d249a39a1881681c303ceea33f38ba1c5bbeb; >= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < 654be81c4c637af12709d47c7efc3302cd336513; >= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < e363c0bc0226dc5ea5046a88e9a6864b82c45399; >= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < 79fdd2aa774e44847cd9bb7edc811e73e3dc7bfe; >= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < 0658b09cba7fe866c6cd70cd2dcdfdcabe80328f; >= 0919e84c0fc1fc73525fdcedefab89ea8460f697, < 0074b82cdfcb5fd13710a0ac308ade68ac6f6fbe
LinuxLinux4.7

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-72289?
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.
How severe is CVE-2026-72289?
CVE-2026-72289 has a CVSS score of 9.3/10 (CRITICAL severity). The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72289?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-72289?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST