CVE-2026-89907

Description

A flaw was found in the Linux kernel's LoongArch KVM (Kernel-based Virtual Machine) component. A local attacker, by controlling a process with a virtual machine file descriptor, could provide unvalidated Message Signaled Interrupt (MSI) data. This unvalidated data is then used as an interrupt number, leading to an out-of-bounds write. This could allow the attacker to corrupt kernel memory, potentially leading to system instability or further compromise.

Statement

This vulnerability is rated as Moderate severity because exploitation requires local access with existing privileges to interact with virtual machine file descriptors, limiting the immediate blast radius. Additionally, the flaw resides entirely within the KVM subsystem for the LoongArch hardware architecture, which is not an architecture supported or enabled across Red Hat Enterprise Linux releases. Supported Red Hat environments therefore do not ship the vulnerable code paths or face operational exposure from this defect.

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 Score5.5N/A8.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/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:L/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; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.