CVE-2026-72288

KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling

State
Published
Severity
9.3 Critical
Published
Aug 15, 2026
Updated
Oct 30, 2026
Reserved
Aug 9, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling

Hyunwoo Kim reports some really bad races should the following situation occur:

- LPI-I is pending in vcpu-B's AP list - vcpu-A writes to vcpu-B's RD to disable its LPIs - vcpu-C moves I from B to C

If the last two race nicely enough, vgic_prune_ap_list() can drop the irq and AP list locks, reacquire them, and in the interval the irq has been freed. UAF follows.

The fix is two-fold:

- Before dropping the irq and ap_list locks, take a reference on the irq

- Do not try to handle migration of the pending bit: there is no expectation that this state is retained, as per the architecture

With that, we're sure that the interrupt is still around, and we safely remove it from the AP list as it has no target at this stage (unless another interrupt fires, but that's another story).

Scores

CVSSScoreVectorSource
3.19.3 CriticalCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 5dd4b924e390af426e424d5e52c1b4d1566af817 to before 7328cff91703ac4e93c200b20cebaa36d2f314edAffected
  • 5dd4b924e390af426e424d5e52c1b4d1566af817 to before eb74f3feb68e64cf69f86cb806a15d8cfb6757f4Affected
  • 5dd4b924e390af426e424d5e52c1b4d1566af817 to before 77c61235d66246dd6a5f55587f0afc273d832775Affected
  • 5dd4b924e390af426e424d5e52c1b4d1566af817 to before d19dca8194ebed371e624331c6be2cb73b562cafAffected
  • 5dd4b924e390af426e424d5e52c1b4d1566af817 to before b1a89d12d35a8256d2b170ced0b1c86851f3def2Affected
  • 5dd4b924e390af426e424d5e52c1b4d1566af817 to before 7258770e5814f15e8308ebda82ac9acf6964ba8eAffected
LinuxLinux
  • 4.8Affected
  • before 4.8Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.114 through 6.12.*Not affected
  • 6.18.40 through 6.18.*Not affected
  • 7.1.5 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.