CVE-2026-89916
Last modified
CVE-2026-89916 is a critical-severity vulnerability rated 9.3/10 on the CVSS scale. 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.
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929, < d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd; >= 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929, < 11ee3faab4f1755d126bead9f882e75a7a677860; >= 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929, < 2b7324f3a0c1072b9d578b8d42f199506753f26e |
| Linux | Linux | 6.16 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89916?
How severe is CVE-2026-89916?
How do I fix CVE-2026-89916?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89910In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2026-89911In the Linux kernel, the following vulnerability has been re…7.9
- CVE-2026-89912In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-89913In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-89914In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-89915In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-89917In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89918In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-89919In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-8992An improper certificate validation vulnerability in Ivanti S…8.8
- CVE-2026-89920In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-89921In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-89916?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
