PT-2026-121899
CVE-2026-98927
·
تاريخ النشر
2026-10-23
·
تاريخ التحديث
2026-10-23
الوصف من
الدرجة
N/A
غير متوفرلا تتوفر حاليًا تقييمات أو مقاييس للخطورة. سنحدّث المعلومات المقابلة في الصفحة فور توفرها.
In the Linux kernel, the following vulnerability has been resolved:
KVM: arm64: nv: Fix life cycle of the nested mmus array
The nested mmus array holds the shadow page tables that are used when
a guest is running a nested context. These structures are allocated on
VCPU INIT for whole guest, which implies that they may have to be
relocated as the array grows.
Should a VCPU INIT occur whilst a vcpu is actively running an L2 and
that the allocation requires relocation, that vcpu will still be
running with a pointer to the previous structure, which will have been
freed.
Fix this by turning the array of structures to an array of pointers,
which is now allocated at VM creation, sized to the absolute maximum
that KVM can handle.
In turn, each VCPU INIT contributes S2 MMU PER VCPU to the pool. No
reallocation is ever performed, and the life cycle of each object is
much clearer:
-
the nested mmus array is allocated in kvm init nested(), and freed in kvm arch destroy vm()
-
s2 mmu structures are allocated in kvm vcpu init nested(), and freed on kvm arch flush shadow all()
Finally, the freeing of vcpu->arch.vncr array is made consistent
rather than being done on some failure paths, but not others.
وجدت خطأً في الوصف؟ لديك ما تضيفه؟ لا تتردد في مراسلتنا 👾