Linux kernel vulnerability in VFIO affects virtualization/host security across organizations; widely used core software with high-impact exploitation potential.
CVE-2026-64475
Use-after-free in Linux vfio/pci VGA arbiter registration
Is CVE-2026-64475 being exploited?
Not confirmed. CVE-2026-64475 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-64475?
CVE-2026-64475 is rated High with a CVSS score of 8.8. 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-64475?
Yes. A fix has been recorded for CVE-2026-64475. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64475 affect?
CVE-2026-64475 affects Linux kernel (vfio/pci subsystem), Virtualization hosts using VFIO (KVM/QEMU), PCI device passthrough setups. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64475?
Install vendor kernel updates, reboot hosts, and restrict VFIO device access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel memory corruption via stale VGA arbiter callback, enabling host crash or local privilege escalation.
Patch when possible
- affected>= 87856f9af04eaacf9848710625a4ffee1d020fa9 and < 0f2a35a0c7ea7da347b814750eaa78adf3582381
- affected>= 4aeec3984ddc853f7c65903bde472ffdef738bae and < 8d65decde9afd2bd78bcfffdc0df73b82a0b5509
- affected>= 4aeec3984ddc853f7c65903bde472ffdef738bae and < ef4c38d30b3744e89eb5048218904bb629ea8d47
- affected>= 4aeec3984ddc853f7c65903bde472ffdef738bae and < 9e0a3f642e607848669235f5069f35640abbfc88
- affected>= 4aeec3984ddc853f7c65903bde472ffdef738bae and < 42d758a09d2c46c42357ecde9a5492f015bde2e5
- affected>= 4aeec3984ddc853f7c65903bde472ffdef738bae and < 52adb2dff7ce3d8430e2bdc5988b618a430def85
- affected>= 4aeec3984ddc853f7c65903bde472ffdef738bae and < 278a5659c391fe5afe5f9ce1bad1fd24e90144f1
- affected>= 4aeec3984ddc853f7c65903bde472ffdef738bae and < daedde7f024ecf88bc8e832ed40cf2c795f0796a
- affectedd62dccb417cf972c978bf3c68a7d5e846bcf953e
- affected6694b8daffac5a8661071f085608afc78f7acd08
- affected>= 5.10.37 and < 5.10.261
- affected>= 5.11.21 and < 5.12
- affected>= 5.12.4 and < 5.13
- affected5.13
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.