CVE-2026-98927KVM: arm64: nv: Fix life cycle of the nested_mmus array
- 7.0HighCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.0 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 95% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.
Affected products
- affected 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 – < ea242bdc29e8a8ff0e2447a64b3841114779f3af
- affected 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 – < 81e3f065a6485626f816d791dfd5e00ddd12eff5
- affected 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 – < 512c93f4461b9a3735987f48423d438a9cd49e6a
- affected 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 – < 33346f8960c7bb6a3b4e273b5cfe25c5a8be349f
- affected 6.11
- unaffected < 6.11
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/ea242bdc29e8a8ff0e2447a64b3841114779f3af (opens in a new tab)
- https://git.kernel.org/stable/c/81e3f065a6485626f816d791dfd5e00ddd12eff5 (opens in a new tab)
- https://git.kernel.org/stable/c/512c93f4461b9a3735987f48423d438a9cd49e6a (opens in a new tab)
- https://git.kernel.org/stable/c/33346f8960c7bb6a3b4e273b5cfe25c5a8be349f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108893 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98927)Record last updated .