PoC Monitor
← All CVEs
CVE-2026-89913published 16 Sep 2026 10:32 UTCData: JSON · API

Linux

KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 280771252c1bae0947215c59fb9ea6a8d9f8399d, < 4000462866bc71f16d1bfb3cf8e969f95150cd64
  • >= 280771252c1bae0947215c59fb9ea6a8d9f8399d, < 7631f95297560157d3a9283cb999e3be00103348
  • >= 280771252c1bae0947215c59fb9ea6a8d9f8399d, < d3a2d20b7248ea67465af1cf79c79f90ff70926c
  • >= 280771252c1bae0947215c59fb9ea6a8d9f8399d, < f5b8f203bfc07a5a257dff859e66d2c500f9f509

Fixed in 4000462866bc71f16d1bfb3cf8e969f95150cd64, 7631f95297560157d3a9283cb999e3be00103348, d3a2d20b7248ea67465af1cf79c79f90ff70926c, f5b8f203bfc07a5a257dff859e66d2c500f9f509

Linux Linux
  • 4.12

Fixed in 0, 6.12.114, 6.18.51, 7.2.5, 7.3

Mitigation

Upgrade Linux to 4000462866bc71f16d1bfb3cf8e969f95150cd64 or 7631f95297560157d3a9283cb999e3be00103348 or d3a2d20b7248ea67465af1cf79c79f90ff70926c or f5b8f203bfc07a5a257dff859e66d2c500f9f509 or later.

Upgrade Linux to 0 or 6.12.114 or 6.18.51 or 7.2.5 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published16 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.