From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80665: KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN
Date: Fri, 28 Aug 2026 08:49:42 +0200 [thread overview]
Message-ID: <2026082847-CVE-2026-80665-615f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: nv: Inject SEA if kvm_translate_vncr() can't resolve PFN
kvm_handle_vncr_abort() assumes that s1_walk_result conveys an abort
when kvm_translate_vncr() returns -EFAULT. This is not always the case
as it's possible to encounter 'late' failures on the output of S1
translation, e.g. a GFN outside of the memslots.
Fix it by preparing an external abort before returning from
kvm_translate_vncr(). Get rid of the BUG_ON() in the fault injection
path while at it.
The Linux kernel CVE team has assigned CVE-2026-80665 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 2a359e072596fcb2e9e85017a865e3618a2fe5b5 and fixed in 6.18.40 with commit 4ead4def04659739c399bfcb063f8a906194c79f
Issue introduced in 6.16 with commit 2a359e072596fcb2e9e85017a865e3618a2fe5b5 and fixed in 7.1.5 with commit 53804b6839573c9c6fff5f4cf075d6746267345e
Issue introduced in 6.16 with commit 2a359e072596fcb2e9e85017a865e3618a2fe5b5 and fixed in 7.2 with commit 9f3e83345a56280efffe235c65593c7e544c0fcc
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-80665
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/arm64/include/asm/kvm_nested.h
arch/arm64/kvm/at.c
arch/arm64/kvm/nested.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/4ead4def04659739c399bfcb063f8a906194c79f
https://git.kernel.org/stable/c/53804b6839573c9c6fff5f4cf075d6746267345e
https://git.kernel.org/stable/c/9f3e83345a56280efffe235c65593c7e544c0fcc
reply other threads:[~2026-08-28 6:52 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=2026082847-CVE-2026-80665-615f@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.