In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: nv: Fix life cycle of the nested_mmus array The nested_…
CVE-2026-98927 · GHSA-2374-8v6x-x95c · EUVD-2026-108893 · published 23 Oct 2026
How serious is it
- Severity: high, CVSS score 7 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-98927?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <ea242bdc29e8a8ff0e2447a64b3841114779f3af
- Linux Linux: patch: 7.2.9
- Linux Linux: 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <81e3f065a6485626f816d791dfd5e00ddd12eff5
- Linux Linux: patch: 7.3
- Linux Linux: patch: 6.18.56
- Linux Linux: 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <33346f8960c7bb6a3b4e273b5cfe25c5a8be349f
- Linux Linux: patch: 0
- Linux Linux: 6.11
- Linux Linux: patch: 6.12.113
- Linux Linux: 4f128f8e1aaac189f83d0f828bcdb2986d8d2e51 <512c93f4461b9a3735987f48423d438a9cd49e6a
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/ea242bdc29e8a8ff0e2447a64b3841114779f3af
- git.kernel.org/stable/c/81e3f065a6485626f816d791dfd5e00ddd12eff5
- git.kernel.org/stable/c/512c93f4461b9a3735987f48423d438a9cd49e6a
- git.kernel.org/stable/c/33346f8960c7bb6a3b4e273b5cfe25c5a8be349f
- nvd.nist.gov/vuln/detail/CVE-2026-98927
Merged from ENISA EUVD. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON