7.3

CVE-2025-22013: linux

CVSS: 7.3v3.1HighModified
AliasesUBUNTU-CVE-2025-22013DEBIAN-CVE-2025-22013
Published 08-04-2025Last modified 15-10-2026

Vulnerability summary

CVE-2025-22013 is a high (CVSS 7.3) vulnerability in linux. EPSS estimates a 0.21% chance of exploitation in the next 30 days, higher than 10.8% of scored vulnerabilities.

Overall risk
29/100
0100
Medium · default modelHow is this calculated?
CVSS score
7.3/10
010
High · v3.1 (CVE.org)
EPSS score
0.21%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 31 · Related 28

Timeline

  1. 08-04-2025
    PublishedVulnerability first disclosed.
  2. 15-10-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.21%

Chance of exploitation in the next 30 days

Percentile

11%

Versus all other CVEs

30-day change

0.00 pp

From 0.21% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.21%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Ubuntu110 products
  • linux< 6.8.0-84.84
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 6.8.0-1039.41
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90, < 5289ac43b69c61a49c75720921f2008005a31c43 | ≥ d5f7d3833b534f9e43e548461dba1e60aa82f587, < 04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e | ≥ 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, < 806d5c1e1d2e5502175a24bf70f251648d99c36a | ≥ 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, < 79e140bba70bcacc5fe15bf8c0b958793fd7d56f | ≥ 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, < 900b444be493b7f404898c785d6605b177a093d0 | ≥ 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, < fbc7e61195e23f744814e78524b73b59faa54ab4 | 6.2
  • linux_kernel≥ 6.2, < 6.6.85 | ≥ 6.7, < 6.12.21 | ≥ 6.13, < 6.13.9 | 6.14:rc1 | 6.14:rc2
Debian1 product
  • linux< 6.12.21-1

3 vendors · 113 products

References

28 links
Show all 28 references