What is CVE-2026-89916?

CVE-2026-89916 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.3 out of 10, affecting Linux kernel versions from 6.16 onward and patched in 6.18.51, 7.2.5 and 7.3-rc1. CVE-2026-89916 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-89916?

CVE-2026-89916 has a CVSS score of 9.3 out of 10, rated Critical severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

Is there a patch available for CVE-2026-89916?

Yes, CVE-2026-89916 has been patched. Fixed versions include 6.18.51, 7.2.5 and 7.3-rc1. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-89916 actively exploited?

CVE-2026-89916 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-89916

Critical

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Make VNCR invalidation participate in MMU invalidation retry A VNCR TLB invalidation can occur on one vcpu while another vcpu is faulting in this same page. Without correctly handling this, we can end up with the following scenario: - vcpu A walks the PTs to translate VNCR - before vcpu A is able to grab the MMU lock to insert the TLB, vcpu B updates the S1 PTs with an invalid entry, and issues a TLBI S1E2 for this VA - vcpu A inserts the TLB for something that is now invalid This isn't a new problem, and we manage S2 by having the MMU notifier to bump up mmu_invalidate_seq on invalidation so that the fault can be replayed. We can perform something similar here, and extend invalidate_vncr_va() to update the same counter, clearly indicating that the context has changed under our feet. This is safe as the invalidation always happen while holding the MMU lock for write, and that we sample the sequence number before walking S1.

Package Linux Kernel

Published 2026-09-16

Last modified 2026-09-16

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

9.3

out of 10

Critical

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.16 and later are affected. Fixed in 6.18.51, 7.2.5, 7.3-rc1 and their respective stable series.

Affected from

≥ 6.16

Fixed in

✓ 6.18.51 6.18.x ✓ 7.2.5 7.2.x ✓ 7.3-rc1

References

3 total

Details

CVE ID CVE-2026-89916

Severity Critical

CVSS score 9.3 / 10

CVSS version 3.1

Published 2026-09-16

Modified 2026-09-16

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-89916?

CVE-2026-89916 is a Critical severity Linux kernel vulnerability with a CVSS score of 9.3 out of 10 . It affects Linux kernel versions from 6.16 onward and has been patched in 6.18.51, 7.2.5 and 7.3-rc1. CVE-2026-89916 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-89916?

CVE-2026-89916 has a CVSS score of 9.3 out of 10, rated Critical severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
Is there a patch available for CVE-2026-89916?

Yes. CVE-2026-89916 has been patched. Fixed versions include 6.18.51, 7.2.5 and 7.3-rc1. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-89916 actively exploited?

No. CVE-2026-89916 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.