CVE-2026-98927

KVM: arm64: nv: Fix life cycle of the nested_mmus array

  • High 7.0

Description

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.

Key facts

Published
23 Oct 2026
Last changed
24 Oct 2026
Assigned by
Linux
EPSS
0.154% likely to be exploited in the next 30 days, higher than 4.554% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.0CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 up to but excluding ea242bdc29e8a8ff0e2447a64b3841114779f3af (affected)
  • 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 up to but excluding 81e3f065a6485626f816d791dfd5e00ddd12eff5 (affected)
  • 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 up to but excluding 512c93f4461b9a3735987f48423d438a9cd49e6a (affected)
  • 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 up to but excluding 33346f8960c7bb6a3b4e273b5cfe25c5a8be349f (affected)
LinuxLinux
  • Default status: affected
  • 6.11 (affected)
  • 0 up to but excluding 6.11 (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.9 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References