Skip to content
Heist/ feed
Back to feed
HighFix available

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

Type: advisorySources: OSV

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: 8383741ab

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.21, 6.13.9, 6.6.85
CVEs
CVE-2025-22013
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 20:00 UTC · Revision 1

Source evidence

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

core-osv · Original source

Published 8 Apr 2025, 08:18 UTC

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: 8383741ab

osv:CVE-2025-22013

Kernel

Fixed versions: 6.6.85, 6.12.21, 6.13.9

Complete source record
{
  "id": "e1a0a60c973e687f910cebf924c4766c15b999a1922de51cb52da22ec9fbcd88",
  "url": "https://osv.dev/vulnerability/CVE-2025-22013",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state",
    "summary": "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: 8383741ab",
    "evidence": "osv:CVE-2025-22013",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.6.85",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.21",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.13.9",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2025-22013",
      "aliases": [
        "CVE-2025-22013"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90"
                },
                {
                  "fixed": "5289ac43b69c61a49c75720921f2008005a31c43"
                }
              ]
            },
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "d5f7d3833b534f9e43e548461dba1e60aa82f587"
                },
                {
                  "fixed": "04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e"
                }
              ]
            },
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe"
                },
                {
                  "fixed": "806d5c1e1d2e5502175a24bf70f251648d99c36a"
                },
                {
                  "fixed": "79e140bba70bcacc5fe15bf8c0b958793fd7d56f"
                },
                {
                  "fixed": "900b444be493b7f404898c785d6605b177a093d0"
                },
                {
                  "fixed": "fbc7e61195e23f744814e78524b73b59faa54ab4"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-22013.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.85"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.21"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.13.9"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-22013.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:39.143335010Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e",
        "https://git.kernel.org/stable/c/5289ac43b69c61a49c75720921f2008005a31c43",
        "https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56f",
        "https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36a",
        "https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0",
        "https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/22xxx/CVE-2025-22013.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-22013",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/22xxx/CVE-2025-22013.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-22013",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 506443,
  "published_at": "2025-04-08T08:18:04+00:00"
}