CVE-2025-22013KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.3 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90 before 5289ac43b69c61a49c75720921f2008005a31c43; from d5f7d3833b534f9e43e548461dba1e60aa82f587 before 04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e; from 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe before 806d5c1e1d2e5502175a24bf70f251648d99c36a; 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe builds before 79e140bba70bcacc5fe15bf8c0b958793fd7d56f; from 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe before 900b444be493b7f404898c785d6605b177a093d0; from 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe before fbc7e61195e23f744814e78524b73b59faa54ab4 | CNA record |
linux linux_kernel linux:linux_kernel | from 6.2 before 6.6.85; from 6.7 before 6.12.21; from 6.13 before 6.13.9; 6.14; 6.14 | NVD |
References
- https://git.kernel.org/stable/c/5289ac43b69c61a49c75720921f2008005a31c43patch
- https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82epatch
- https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36apatch
- https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56fpatch
- https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0patch
- https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.