CVE-2026-89913

Description

A flaw was found in the KVM (Kernel-based Virtual Machine) arm64 vgic-v3 component of the Linux kernel. A race condition exists where the vgic_v3_save_pending_tables() function can dereference a freed vgic_irq structure due to improper handling of LPI (Locality-sensitive Paging Interrupt) references. This could allow a local attacker with access to a virtual machine to cause a denial of service or potentially execute arbitrary code.

Statement

A race in KVM arm64 VGICv3 LPI handling can let vgic_v3_save_pending_tables use a stale struct vgic_irq pointer after the LPI was removed from lpi_xa and freed through RCU. The vulnerable path reads LPI fields and performs guest memory operations after only temporary xarray RCU coverage, while a concurrent irqfd cached injection path and guest ITS DISCARD can drop the last LPI reference. For the CVSS the PR:L is used because triggering requires a local user or guest owner with access to a KVM VM or VMM interface rather than full host administrator privileges. The issue is not directly network reachable and is a local virtualization attack surface. Impact is at least denial of service via host kernel crash and in the worst case may allow confidentiality or integrity impact because the bug is a kernel use after free in host context.

Mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.7N/A8.8
Attack VectorLocalN/ALocal
Attack ComplexityHighN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AChanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.