CVE-2026-31564

LoongArch: KVM: Fix base address calculation in kvm_eiointc_regs_access()

Published Apr 24, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

LoongArch: KVM: Fix base address calculation in kvm_eiointc_regs_access()

In function kvm_eiointc_regs_access(), the register base address is
caculated from array base address plus offset, the offset is absolute
value from the base address. The data type of array base address is
u64, it should be converted into the "void *" type and then plus the
offset.

Analysis

AI-generated

Technical impact

In the LoongArch KVM implementation of the Linux kernel, the base address for a register in kvm_eiointc_regs_access() is calculated incorrectly. The function adds an offset directly to a 64‑bit base address value instead of first converting the base address to a pointer type, resulting in a type misuse categorized as CWE‑681. This incorrect calculation can lead to the use of out‑of‑bounds memory addresses, potentially corrupting kernel memory and causing instability such as kernel panics.

Affected Systems

The flaw affects the Linux kernel across versions 6.19 and all 7.0 release candidates up to and including 7.0‑rc7 when running on LoongArch hardware with the KVM hypervisor. Users running these kernel releases on affected systems are impacted until the code path is removed by the patch.

Risk and Exploitability

With a CVSS score of 5.5 the vulnerability is of moderate severity. The EPSS score is below 1 %, indicating a low likelihood of exploitation at present, and the flaw is not listed in CISA’s KEV catalog. Based on the description, it is inferred that exploiting the bug would require access to the vulnerable KVM subsystem and the ability to influence the address calculation, implying a local or privileged context rather than a wide‑range remote attack vector. The primary risk remains kernel memory corruption and potential system instability.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the fixed base‑address calculation for LoongArch KVM.
  • Ensure that all KVM virtual machines boot with the updated kernel image so the vulnerable code path is not exercised.
  • If a kernel upgrade is not immediately feasible, monitor the system for signs of kernel instability or abnormal memory corruption and plan a rapid update as soon as possible.

Generated by OpenCVE AI on April 28, 2026 at 14:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Fix base address calculation in kvm_eiointc_regs_access() In function kvm_eiointc_regs_access(), the register base address is caculated from array base address plus offset, the offset is absolute value from the base address. The data type of array base address is u64, it should be converted into the "void *" type and then plus the offset.
Title LoongArch: KVM: Fix base address calculation in kvm_eiointc_regs_access()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
May 11, 2026, 10:11 PM
Reserved
Mar 9, 2026, 3:48 PM
Status
Analyzed
Published
Apr 24, 2026, 3:16 PM
Modified
Nov 11, 2026, 11:10 PM
Severity
Public date
Apr 24, 2026, 12:00 AM