From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89911: KVM: arm64: Correctly cap TLBI Range to the architural limit
Date: Wed, 16 Sep 2026 11:30:41 +0100 [thread overview]
Message-ID: <2026091641-CVE-2026-89911-caaa@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: Correctly cap TLBI Range to the architural limit
TLB Invalidation by Range has a fairly powerful way of encoding pretty
large ranges in a small number of bits. This range can be based on an
arbitrary VA, which means it is pretty easy for a guest to generate an
overflow should the hypervisor be naive enough to add the range to the
base...
Make sure the range is capped to the limit dictated by the address bit
that determines the VA range. For an IPA invalidation, this is further
corrected down the line to ignore the upper range.
The Linux kernel CVE team has assigned CVE-2026-89911 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 and fixed in 6.18.51 with commit 566b1f08d983615f731cc693f2ad59db302c6b57
Issue introduced in 6.16 with commit 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 and fixed in 7.2.5 with commit 2de38f0448b45d27eba984fc0d9edb7a138972c2
Issue introduced in 6.16 with commit 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 and fixed in 7.3-rc1 with commit 69a598288195947a1662b53de702eb6976af96b7
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-89911
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
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/566b1f08d983615f731cc693f2ad59db302c6b57
https://git.kernel.org/stable/c/2de38f0448b45d27eba984fc0d9edb7a138972c2
https://git.kernel.org/stable/c/69a598288195947a1662b53de702eb6976af96b7
reply other threads:[~2026-09-16 10:38 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=2026091641-CVE-2026-89911-caaa@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.