KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling
CVE-2026-72288 · published 15 Aug 2026
How serious is it
- Severity: critical, CVSS score 9.3 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-72288?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 5dd4b924e390af426e424d5e52c1b4d1566af817 to < eb74f3feb68e64cf69f86cb806a15d8cfb6757f4, 5dd4b924e390af426e424d5e52c1b4d1566af817 to < 77c61235d66246dd6a5f55587f0afc273d832775, 5dd4b924e390af426e424d5e52c1b4d1566af817 to < d19dca8194ebed371e624331c6be2cb73b562caf, 5dd4b924e390af426e424d5e52c1b4d1566af817 to < b1a89d12d35a8256d2b170ced0b1c86851f3def2
- Linux Linux: 4.8
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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).
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/eb74f3feb68e64cf69f86cb806a15d8cfb6757f4
- git.kernel.org/stable/c/77c61235d66246dd6a5f55587f0afc273d832775
- git.kernel.org/stable/c/d19dca8194ebed371e624331c6be2cb73b562caf
- git.kernel.org/stable/c/b1a89d12d35a8256d2b170ced0b1c86851f3def2
- git.kernel.org/stable/c/7258770e5814f15e8308ebda82ac9acf6964ba8e
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON