Hypervisor-level Linux kernel KVM bug on arm64 can enable guest-triggered kernel memory corruption or guest-to-host escape; impacts virtualization infrastructure used across organizations.
CVE-2026-64106
Linux KVM (arm64) vgic-its restore accepts out-of-range EventID bits enabling host memory corruption.
Is CVE-2026-64106 being exploited?
Not confirmed. CVE-2026-64106 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-64106?
CVE-2026-64106 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-64106?
Yes. A fix has been recorded for CVE-2026-64106. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64106 affect?
CVE-2026-64106 affects Linux kernel (KVM on arm64) vgic-its, KVM/QEMU hypervisors on ARM hosts, Cloud VM hosts using arm64 virtualization. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64106?
Apply vendor Linux kernel/hypervisor patches immediately; isolate untrusted guests.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Guest-controlled ITS restore can cause kernel memory corruption, leading to host crash or potential guest-to-host escape/privilege escalation.
Immediate action required
- affected>= 57a9a117154c93539e33161dd318e6aeb8c04efa and < 1716b7fea2ead941a0dfac06c4504a3437cdf00d
- affected>= 57a9a117154c93539e33161dd318e6aeb8c04efa and < dab9f93251b2c86a033de6098d0c73afddd55d4a
- affected>= 57a9a117154c93539e33161dd318e6aeb8c04efa and < b94538186a3eae3763b8f96dacd610920a865aa7
- affected>= 57a9a117154c93539e33161dd318e6aeb8c04efa and < 0680f511926589206f81f57f76ce131d7741a316
- affected>= 57a9a117154c93539e33161dd318e6aeb8c04efa and < 8bcd15b690a390241179516af1b6ae49ebfd9d95
- affected>= 57a9a117154c93539e33161dd318e6aeb8c04efa and < 9ce754ed8e7ab4e3999767ce1505f85c449ccb07
- affected4.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.