https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 02:55:37 +0000 https://vulnerability.circl.lu/vuln/cve-2026-46317 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: arm64: Reassign nested_mmus array behind mmu_lock</p> <p>kvm-&gt;arch.nested_mmus[] is walked under kvm-&gt;mmu_lock, including from the MMU notifier path (kvm_unmap_gfn_range() -&gt; kvm_nested_s2_unmap()), which can run at any time. kvm_vcpu_init_nested() reallocates the array and frees the old buffer while holding only kvm-&gt;arch.config_lock, so such a walker can reference the freed array.</p> <p>Allocate the new array outside of mmu_lock, as the allocation can sleep. Under the lock, copy the existing entries, fix up the back pointers and reassign the array. Free the old buffer after dropping the lock, as kvfree() can sleep as well.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: arm64: Reassign nested_mmus array behind mmu_lock</p> <p>kvm-&gt;arch.nested_mmus[] is walked under kvm-&gt;mmu_lock, including from the MMU notifier path (kvm_unmap_gfn_range() -&gt; kvm_nested_s2_unmap()), which can run at any time. kvm_vcpu_init_nested() reallocates the array and frees the old buffer while holding only kvm-&gt;arch.config_lock, so such a walker can reference the freed array.</p> <p>Allocate the new array outside of mmu_lock, as the allocation can sleep. Under the lock, copy the existing entries, fix up the back pointers and reassign the array. Free the old buffer after dropping the lock, as kvfree() can sleep as well.</p> https://vulnerability.circl.lu/vuln/cve-2026-46317