CVE-2026-89913KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables
- 8.8HighCVSS 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-v3: take an LPI reference in vgic_v3_save_pending_tables vgic_v3_save_pending_tables() iterates dist->lpi_xa using xa_for_each() and dereferences the returned struct vgic_irq in the loop body without holding a reference on the LPI. The xarray iterator only provides temporary RCU coverage while looking up the current entry. That is not sufficient for this loop body, which reads fields from struct vgic_irq and performs guest memory accesses before the iteration completes. A concurrent path can trigger this race: the irqfd cached injection path (vgic_its_inject_cached_translation) obtains a transient LPI reference via vgic_its_check_cache() without holding kvm->lock, vcpu->mutex, config_lock, or its_lock. If guest ITS DISCARD then drops the cache and ITE references under its_lock, the transient inject reference may become the final one. When vgic_put_irq() drops it, the LPI is erased from lpi_xa and freed via kfree_rcu(). Meanwhile, vgic_v3_save_pending_tables() may still hold a stale pointer obtained from the xarray iterator and dereference it after the RCU grace period completes. Fix this by re-fetching each iterated LPI via vgic_get_irq(), which takes a stable reference, and dropping it with vgic_put_irq() on all paths. This matches the pattern already used by other lpi_xa iterators in the vgic ITS code.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 35 days later
· 35 days 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 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (13 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected 280771252c1bae0947215c59fb9ea6a8d9f8399d – < 4000462866bc71f16d1bfb3cf8e969f95150cd64
- affected 280771252c1bae0947215c59fb9ea6a8d9f8399d – < 7631f95297560157d3a9283cb999e3be00103348
- affected 280771252c1bae0947215c59fb9ea6a8d9f8399d – < d3a2d20b7248ea67465af1cf79c79f90ff70926c
- affected 280771252c1bae0947215c59fb9ea6a8d9f8399d – < f5b8f203bfc07a5a257dff859e66d2c500f9f509
- affected 4.12
- unaffected < 4.12
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/4000462866bc71f16d1bfb3cf8e969f95150cd64 (opens in a new tab)
- https://git.kernel.org/stable/c/7631f95297560157d3a9283cb999e3be00103348 (opens in a new tab)
- https://git.kernel.org/stable/c/d3a2d20b7248ea67465af1cf79c79f90ff70926c (opens in a new tab)
- https://git.kernel.org/stable/c/f5b8f203bfc07a5a257dff859e66d2c500f9f509 (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-80513 (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-89913)Record last updated .