CVE-2026-46317CWE-416

CVE-2026-46317

High · published June 9, 2026

CVSS v3.1
8.8
EPSS
0%
Percentile
2.0
In the wild
Unconfirmed
What it is

In the Linux kernel, the following vulnerability has been resolved:

KVM: arm64: Reassign nested_mmus array behind mmu_lock

kvm->arch.nested_mmus[] is walked under kvm->mmu_lock, including from the

MMU notifier path (kvm_unmap_gfn_range() -> 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->arch.config_lock, so such a walker

can reference the freed array.

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.

The record
Technical detail
CVSS v3.1
8.8 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00125 · 2.0th percentile
Weakness
CWE-416 · Use After Free
Published
2026-06-09T17:16Z
Affected products (8)
ProductVersionsFixed in
linux/linux_kernel≥ 6.11, < 6.18.356.18.35
linux/linux_kernel≥ 6.19, < 7.0.127.0.12
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
linux/linux_kernelall versions—
References (3)
EPSS history
Timeline
  • 09 JUN 11:52Z
    KVM: arm64: Reassign nested_mmus array behind mmu_lock
    cvelistv5