CVE-2026-98927·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.12.113, 6.18.56, 7.2.9, 7.3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.15% — higher than 4% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-98927 scores 7 on CVSS, so a successful attack would be serious — but at 0.15%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched version to resolve a memory safety issue in KVM's nested virtualization handling. Systems running kernel 6.12, 6.18, or 7.2 should upgrade to versions 6.12.113, 6.18.56, or 7.2.9 respectively. Alternatively, install your distribution's patched kernel package rather than upgrading to mainline 7.3.
sudo dnf update kernelDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with: uname -r
- Step 2: Verify if KVM is enabled and in use with: grep -E 'kvm|KVM' /proc/cpuinfo && lsmod | grep kvm
- Step 3: Review kernel logs for memory allocation failures or page table errors with: sudo journalctl -k | grep -iE 'nested_mmu|s2_mmu|allocation|page_table' | tail -50
- Step 4: After patching, confirm the new kernel version is running with: uname -r and verify it matches 6.12.113+, 6.18.56+, or 7.2.9+
FAQ
What is CVE-2026-98927?
This is a memory management vulnerability in the Linux kernel's KVM nested virtualization implementation where the nested_mmus array could become invalid if reallocated while a vCPU is actively running a nested guest context, potentially causing use-after-free conditions.
Is CVE-2026-98927 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available.
What versions of Kernel are affected by CVE-2026-98927?
Vulnerable versions include kernels before 6.12.113, 6.18.56, and 7.2.9 across their respective stable branches. The exact initial vulnerable version depends on when nested virtualization support was introduced for your architecture.
How do I check if my server is vulnerable to CVE-2026-98927?
Run: uname -r to get your kernel version, then compare it against the patched versions (6.12.113, 6.18.56, 7.2.9). If your version is older than the corresponding patched release for your branch, you are vulnerable.
Does Defensia detect CVE-2026-98927?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-98927 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98927. Free for 1 server.
Get started free