Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-22013

KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-22013, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90 – < 5289ac43b69c61a49c75720921f2008005a31c43
    • affected d5f7d3833b534f9e43e548461dba1e60aa82f587 – < 04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e
    • affected 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe – < 806d5c1e1d2e5502175a24bf70f251648d99c36a
    • affected 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe – < 79e140bba70bcacc5fe15bf8c0b958793fd7d56f
    • affected 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe – < 900b444be493b7f404898c785d6605b177a093d0
    • affected 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe – < fbc7e61195e23f744814e78524b73b59faa54ab4

  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 6.6.85 – ≤ 6.6.*
    • unaffected 6.12.21 – ≤ 6.12.*
    • unaffected 6.13.9 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-22013 badge
[![CVE-2025-22013](https://cveledger.app/badge/CVE-2025-22013.svg)](https://cveledger.app/cve/CVE-2025-22013)

Record last updated .