{"id":"CVE-2026-98927","title":"KVM: arm64: nv: Fix life cycle of the nested_mmus array","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: nv: Fix life cycle of the nested_mmus array\n\nThe nested_mmus array holds the shadow page tables that are used when\na guest is running a nested context. Thes…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < ea242bdc29e8a8ff0e2447a64b3841114779f3af","Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 81e3f065a6485626f816d791dfd5e00ddd12eff5","Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 512c93f4461b9a3735987f48423d438a9cd49e6a","Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 33346f8960c7bb6a3b4e273b5cfe25c5a8be349f","Linux 6.11"],"published":"2026-10-23","updated":"2026-10-23","sourceUpdated":"2026-10-23T12:06:01.528Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-98927","references":[{"url":"https://git.kernel.org/stable/c/ea242bdc29e8a8ff0e2447a64b3841114779f3af"},{"url":"https://git.kernel.org/stable/c/81e3f065a6485626f816d791dfd5e00ddd12eff5"},{"url":"https://git.kernel.org/stable/c/512c93f4461b9a3735987f48423d438a9cd49e6a"},{"url":"https://git.kernel.org/stable/c/33346f8960c7bb6a3b4e273b5cfe25c5a8be349f"}],"tags":["cve.org"],"ingestedAt":"2026-10-23T13:24:55.566Z","slug":"CVE-2026-98927","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: nv: Fix life cycle of the nested_mmus array\n\nThe nested_mmus array holds the shadow page tables that are used when\na guest is running a nested context. These structures are allocated on\nVCPU_INIT for whole guest, which implies that they may have to be\nrelocated as the array grows.\n\nShould a VCPU_INIT occur whilst a vcpu is actively running an L2 and\nthat the allocation requires relocation, that vcpu will still be\nrunning with a pointer to the previous structure, which will have been\nfreed.\n\nFix this by turning the array of structures to an array of pointers,\nwhich is now allocated at VM creation, sized to the absolute maximum\nthat KVM can handle.\n\nIn turn, each VCPU_INIT contributes S2_MMU_PER_VCPU to the pool. No\nreallocation is ever performed, and the life cycle of each object is\nmuch clearer:\n\n- the nested_mmus array is allocated in kvm_init_nested(), and freed\n  in kvm_arch_destroy_vm()\n\n- s2_mmu structures are allocated in kvm_vcpu_init_nested(), and freed\n  on kvm_arch_flush_shadow_all()\n\nFinally, the freeing of vcpu->arch.vncr_array is made consistent\nrather than being done on some failure paths, but not others.\n\n## Affected\n\n- `Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < ea242bdc29e8a8ff0e2447a64b3841114779f3af`\n- `Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 81e3f065a6485626f816d791dfd5e00ddd12eff5`\n- `Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 512c93f4461b9a3735987f48423d438a9cd49e6a`\n- `Linux >= 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 < 33346f8960c7bb6a3b4e273b5cfe25c5a8be349f`\n- `Linux 6.11`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}