CVE-2026-89916

CVE CVE-2026-89916EUVD EUVD-2026-80516Published 2026-09-16T10:32:11.000ZLast changed 2026-09-16T14:40:09.000ZCVSS 9.3

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <2b7324f3a0c1072b9d578b8d42f199506753f26e; 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <d8580e7aa189b0c6c5bb4d94b8352728a7c35bbd; patch: 7.3-rc1; 4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 <11ee3faab4f1755d126bead9f882e75a7a677860; patch: 0; patch: 7.2.5; patch: 6.18.51; 6.16

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.