SECUFOCUSNOW
Home›CVE index›CVE-2026-46317
Review reviewHigh

CVE-2026-46317

Linux Linux, linux kernel

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...

CVSS
8.8
EPSS
0.13%
3.03% percentile
CISA KEV
Not listed
Published
2026.06.09
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 8.8

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 918450ad6010df6ecd2efde12a1409e011da22d6, >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 4424dbcb06d68e34e51c019a5781a7dc00731971, >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 70543358fa08e0f7cebc3447c3b70fe97ad7aaa8, >= 6.11, >= 6.11 < 6.18.35, >= 6.19 < 7.0.12, 7.1
Fixed versions
6.18.35, 7.0.12

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CWE
Not available