cve.bz

CVE-2026-89918 linux linux

9.3 criticalEPSS 0.2%Fix available

Critical (9.3) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Correctly handle end of VA space TLBI invalidation Our TLB invalidation by VA code is based on comparing two ranges, one defined by the TLB, and one defined by the TLBI instruction. Each range is defined by a start and a size. However, the way the comparison is done doesn't account for address rollover, as it compares an address with (base + size). This works nicely until this expression represent the last page/block in the TTBR1 VA space, as the result is a big fat 0. And a failed TLB invalidation. Rewrite the comparison in a way that is immune to the address rollover (making the end address inclusive instead of exclusive), and move this into a common helper that is used by both VA and IPA invalidations, as suggested by Hyunwoo Kim (although the IPA version didn't suffer from this particular problem, obviously).

Severity

CVSS 3.1

9.3 critical
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-89918 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-89918?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-89918?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-89918 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.16 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.51
Linux7.27.2.5
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.2.6-1DEBIAN-CVE-2026-89918
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-89918
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-89918
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-89918
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-89918
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-89918 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-89918 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-89918 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-89918 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-89918 USN-9020-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 27 moreno fix listedUBUNTU-CVE-2026-89918
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-89918
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-89918 USN-8959-1
12 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.7-1.1openSUSE-SU-2026:11880-1
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-89918

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

KVM arm64 nested virtualization can miss a VA based TLBI invalidation at the end of the TTBR1 VA space because the range comparison used base plus size and did not handle address rollover. A guest controlled TLBI range that reaches the end of the VA space may therefore leave a stale VNCR TLB entry active and later KVM code may use an obsolete translation. For the CVSS the PR:L value is used because reliable triggering requires local KVM access or control of a guest context rather than a remote packet only interface. The issue is not directly network reachable and depends on arm64 nested virtualization support and the affected VNCR TLBI path. Impact is at least denial of service or guest memory integrity impact from stale translation use.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-89918.

References

Check your stackJSON