From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72294: LoongArch: KVM: Check irq validity in kvm_vcpu_ioctl_interrupt()
Date: Sat, 15 Aug 2026 15:06:13 +0900 [thread overview]
Message-ID: <2026081501-CVE-2026-72294-ef9a@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
LoongArch: KVM: Check irq validity in kvm_vcpu_ioctl_interrupt()
Function kvm_vcpu_ioctl_interrupt() can be called from userspace, here
add irq validility cheking in kvm_vcpu_ioctl_interrupt().
The Linux kernel CVE team has assigned CVE-2026-72294 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit f45ad5b8aa9335bc6b30331b739e778f2f730b35 and fixed in 6.12.97 with commit 15469ba0284c7cc01c38493391e9e73b918833c4
Issue introduced in 6.7 with commit f45ad5b8aa9335bc6b30331b739e778f2f730b35 and fixed in 6.18.40 with commit efe27b19a15c384cad7c80de399f3107ab070e6d
Issue introduced in 6.7 with commit f45ad5b8aa9335bc6b30331b739e778f2f730b35 and fixed in 7.1.5 with commit d4574547e04a47ad498149576f65b84475ea6f4c
Issue introduced in 6.7 with commit f45ad5b8aa9335bc6b30331b739e778f2f730b35 and fixed in 7.2-rc1 with commit 09b318ab77b7a4fc9987fd98d1525fc55ddc2617
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-72294
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/loongarch/kvm/vcpu.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/15469ba0284c7cc01c38493391e9e73b918833c4
https://git.kernel.org/stable/c/efe27b19a15c384cad7c80de399f3107ab070e6d
https://git.kernel.org/stable/c/d4574547e04a47ad498149576f65b84475ea6f4c
https://git.kernel.org/stable/c/09b318ab77b7a4fc9987fd98d1525fc55ddc2617
reply other threads:[~2026-08-15 6:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081501-CVE-2026-72294-ef9a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.