---
id: "CVE-2026-98712"
kind: "vulnerability"
aliases: ["CVE-2026-98712"]
title: "Linux KVM arm64: stale interrupt reference can crash or corrupt guest interrupt handling"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["arm64", "hypervisor", "infrastructure", "kvm", "linux-kernel"]
not_affected_if: ["no-kvm", "x86-host"]
published_at: "2026-10-18T16:17:24+00:00"
first_seen_at: "2026-10-23T21:57:16+00:00"
updated_at: "2026-10-25T05:17:31+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98712", "first_seen_at": "2026-10-23T21:57:16+00:00"}]
---

# Linux KVM arm64: stale interrupt reference can crash or corrupt guest interrupt handling

In the Linux kernel's arm64 KVM virtual interrupt controller, the last interrupt inserted into a list register could be freed when a mapped LPI was unmapped concurrently, leaving a dangling reference. The fix takes a reference count on that interrupt and drops it when LPIs are reclaimed.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- unknown

## Fix

- unknown

## Timeline

- 2026-10-23T21:57:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98712

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: vgic: Take a refcount on IRQs referenced by last_lr_irq

Referencing the last interrupt inserted in an LR is rather fragile, as
this interrupt can vanish if a concurrently unmapped LPI.

Solve this by bumping up the refcount on the interrupt when populating
last_lr_irq, and drop it at vgic_prune_ap_list() time, when LPIs are
being reclaimed.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_