CVE-2026-72288KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling
- 9.3CriticalCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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).
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | Critical9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | Critical9.3 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.3.
Affected products
- affected 5dd4b924e390af426e424d5e52c1b4d1566af817 – < 7328cff91703ac4e93c200b20cebaa36d2f314ed
- affected 5dd4b924e390af426e424d5e52c1b4d1566af817 – < eb74f3feb68e64cf69f86cb806a15d8cfb6757f4
- affected 5dd4b924e390af426e424d5e52c1b4d1566af817 – < 77c61235d66246dd6a5f55587f0afc273d832775
- affected 5dd4b924e390af426e424d5e52c1b4d1566af817 – < d19dca8194ebed371e624331c6be2cb73b562caf
- affected 5dd4b924e390af426e424d5e52c1b4d1566af817 – < b1a89d12d35a8256d2b170ced0b1c86851f3def2
- affected 5dd4b924e390af426e424d5e52c1b4d1566af817 – < 7258770e5814f15e8308ebda82ac9acf6964ba8e
- affected 4.8
- unaffected < 4.8
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/7328cff91703ac4e93c200b20cebaa36d2f314ed (opens in a new tab)
- https://git.kernel.org/stable/c/eb74f3feb68e64cf69f86cb806a15d8cfb6757f4 (opens in a new tab)
- https://git.kernel.org/stable/c/77c61235d66246dd6a5f55587f0afc273d832775 (opens in a new tab)
- https://git.kernel.org/stable/c/d19dca8194ebed371e624331c6be2cb73b562caf (opens in a new tab)
- https://git.kernel.org/stable/c/b1a89d12d35a8256d2b170ced0b1c86851f3def2 (opens in a new tab)
- https://git.kernel.org/stable/c/7258770e5814f15e8308ebda82ac9acf6964ba8e (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59187 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72288)Record last updated .