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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 to < d8580e7aa189b0c6c5bb4d94b8352728a7c35bbdaffected4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 to < 11ee3faab4f1755d126bead9f882e75a7a677860affected4ffa72ad8f37e73bbb6c0baa88557bcb4fd39929 to < 2b7324f3a0c1072b9d578b8d42f199506753f26eaffected
Linux Linux
Default version status: affected
6.16affected0 to < 6.16unaffected6.18.51 to ≤ 6.18.*unaffected7.2.5 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected