Vulnerability · Published Apr 8, 2025 · Assigned by Linux

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

High 7.3

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.3High
Exploit odds (30 days)0.2%top 87.9% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.21-1DEBIAN-CVE-2025-22013
Debian:14linux6.12.21-1DEBIAN-CVE-2025-22013
Ubuntu:24.04:LTSlinux6.8.0-84.84UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-aws6.8.0-1039.41UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1039.41~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-azure6.8.0-1038.44UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1018.18~24.04.1UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1036.42~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-azure-nvidia6.8.0-1025.27UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-gcp6.8.0-1040.42UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1016.16~24.04.1UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1040.42~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-gke6.8.0-1036.40UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1023.25UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-28.28~24.04.1UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-85.85~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-ibm6.8.0-1037.37UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1037.37~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-84.84.1UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1015.16~24.04.2UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-84.84.1~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1039.42UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1012.12UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1039.42~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1039.42.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1010.10UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1024.24UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-oracle6.8.0-1037.38UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1037.38~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-raspi6.8.0-1039.43UBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-84.84~22.04.1UBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-22013
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-22013
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1018.19UBUNTU-CVE-2025-22013

Affected products (as reported)

VendorProductVersions
Linux Linux c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90 – before 5289ac43b69c61a49c75720921f2008005a31c43d5f7d3833b534f9e43e548461dba1e60aa82f587 – before 04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e93ae6b01bafee8fa385aa25ee7ebdb40057f6abe – before 806d5c1e1d2e5502175a24bf70f251648d99c36a93ae6b01bafee8fa385aa25ee7ebdb40057f6abe – before 79e140bba70bcacc5fe15bf8c0b958793fd7d56f93ae6b01bafee8fa385aa25ee7ebdb40057f6abe – before 900b444be493b7f404898c785d6605b177a093d093ae6b01bafee8fa385aa25ee7ebdb40057f6abe – before fbc7e61195e23f744814e78524b73b59faa54ab4
Linux Linux 6.2

References