GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2025-22013 (GCVE-0-2025-22013)

Vulnerability from cvelistv5 – Published: 2025-04-08 08:18 – Updated: 2026-08-05 11:55
VLAI
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: 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.
Severity
7.3 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90 , < 5289ac43b69c61a49c75720921f2008005a31c43 (git)
Affected: d5f7d3833b534f9e43e548461dba1e60aa82f587 , < 04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e (git)
Affected: 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe , < 806d5c1e1d2e5502175a24bf70f251648d99c36a (git)
Affected: 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe , < 79e140bba70bcacc5fe15bf8c0b958793fd7d56f (git)
Affected: 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe , < 900b444be493b7f404898c785d6605b177a093d0 (git)
Affected: 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe , < fbc7e61195e23f744814e78524b73b59faa54ab4 (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.2
Unaffected: 0 , < 6.2 (semver)
Unaffected: 6.6.85 , ≤ 6.6.* (semver)
Unaffected: 6.12.21 , ≤ 6.12.* (semver)
Unaffected: 6.13.9 , ≤ 6.13.* (semver)
Unaffected: 6.14 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/arm64/kernel/fpsimd.c",
            "arch/arm64/kvm/fpsimd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5289ac43b69c61a49c75720921f2008005a31c43",
              "status": "affected",
              "version": "c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90",
              "versionType": "git"
            },
            {
              "lessThan": "04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e",
              "status": "affected",
              "version": "d5f7d3833b534f9e43e548461dba1e60aa82f587",
              "versionType": "git"
            },
            {
              "lessThan": "806d5c1e1d2e5502175a24bf70f251648d99c36a",
              "status": "affected",
              "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
              "versionType": "git"
            },
            {
              "lessThan": "79e140bba70bcacc5fe15bf8c0b958793fd7d56f",
              "status": "affected",
              "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
              "versionType": "git"
            },
            {
              "lessThan": "900b444be493b7f404898c785d6605b177a093d0",
              "status": "affected",
              "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
              "versionType": "git"
            },
            {
              "lessThan": "fbc7e61195e23f744814e78524b73b59faa54ab4",
              "status": "affected",
              "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/arm64/kernel/fpsimd.c",
            "arch/arm64/kvm/fpsimd.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.2"
            },
            {
              "lessThan": "6.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.85",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.21",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.85",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.21",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.9",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state\n\nThere are several problems with the way hyp code lazily saves the host\u0027s\nFPSIMD/SVE state, including:\n\n* Host SVE being discarded unexpectedly due to inconsistent\n  configuration of TIF_SVE and CPACR_ELx.ZEN. This has been seen to\n  result in QEMU crashes where SVE is used by memmove(), as reported by\n  Eric Auger:\n\n  https://issues.redhat.com/browse/RHEL-68997\n\n* Host SVE state is discarded *after* modification by ptrace, which was an\n  unintentional ptrace ABI change introduced with lazy discarding of SVE state.\n\n* The host FPMR value can be discarded when running a non-protected VM,\n  where FPMR support is not exposed to a VM, and that VM uses\n  FPSIMD/SVE. In these cases the hyp code does not save the host\u0027s FPMR\n  before unbinding the host\u0027s FPSIMD/SVE/SME state, leaving a stale\n  value in memory.\n\nAvoid these by eagerly saving and \"flushing\" the host\u0027s FPSIMD/SVE/SME\nstate when loading a vCPU such that KVM does not need to save any of the\nhost\u0027s FPSIMD/SVE/SME state. For clarity, fpsimd_kvm_prepare() is\nremoved and the necessary call to fpsimd_save_and_flush_cpu_state() is\nplaced in kvm_arch_vcpu_load_fp(). As \u0027fpsimd_state\u0027 and \u0027fpmr_ptr\u0027\nshould not be used, they are set to NULL; all uses of these will be\nremoved in subsequent patches.\n\nHistorical problems go back at least as far as v5.17, e.g. erroneous\nassumptions about TIF_SVE being clear in commit:\n\n  8383741ab2e773a9 (\"KVM: arm64: Get rid of host SVE tracking/saving\")\n\n... and so this eager save+flush probably needs to be backported to ALL\nstable trees."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.3,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerable path is `kvm_arch_vcpu_load_fp()`/`kvm_arch_vcpu_put_fp()`, reached only through the `KVM_RUN` ioctl on `/dev/kvm` from a local process on the host. No network or adjacent-network input reaches this code.\nAC:L - The attacker deterministically controls every condition: enabling SVE in its own thread, issuing `KVM_RUN` with a guest that never touches FP/SIMD (so `guest_owns_fp_regs()` is false and no flush occurs), and then executing SVE code after return. CONFIG_ARM64_SVE is default-y and SVE-capable hardware (ARMv9, Neoverse V1/V2, Graviton 3/4, Ampere) is mainstream.\nPR:L - Only an unprivileged local account with access to `/dev/kvm` is needed \u2014 systemd\u0027s default udev rule installs it as `MODE=\"0666\"`, and Android AVF/ChromeOS crosvm expose VM creation to unprivileged apps. No root, CAP_SYS_ADMIN, or init-namespace capability is required.\nUI:N - The attacking process performs the entire sequence itself \u2014 set up SVE, call `KVM_RUN`, return, run SVE code \u2014 with no action by any other user or administrator.\nS:U - The mismanaged FPSIMD/SVE/SME context belongs to the same host task that invoked `KVM_RUN`, and the kernel remains the single security authority over both the vulnerable KVM/fpsimd code and the impacted host process; this is not a guest-to-host escape or an IOMMU bypass.\nC:L - `fpsimd_kvm_prepare()` populates `uw.fpsimd_state` from the stale in-memory `thread.sve_state` while the live values sit in registers, so a stale register snapshot can resurface in signal frames/core dumps, and SVE-accelerated string/memory routines running with silently discarded vector state can process and emit unintended buffer contents \u2014 a bounded, indirect disclosure rather than arbitrary memory read.\nI:H - Host SVE/FPMR register state is silently corrupted mid-computation outside any ABI-sanctioned discard point, so SVE-based `memmove()`/`memcpy()` in glibc write wrong data into arbitrary destinations, producing memory corruption inside the affected process (the observed QEMU failures); it also silently drops SVE register values written via ptrace, breaking the debugger/CRIU ABI.\nA:H - The corruption reliably crashes the affected process \u2014 the reported real-world symptom is QEMU aborting when SVE-based `memmove()` copies garbage \u2014 killing the VM and its workload, and it can be re-triggered at will by any local user with `/dev/kvm`."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:55:59.327Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/5289ac43b69c61a49c75720921f2008005a31c43"
        },
        {
          "url": "https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e"
        },
        {
          "url": "https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36a"
        },
        {
          "url": "https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56f"
        },
        {
          "url": "https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0"
        },
        {
          "url": "https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4"
        }
      ],
      "title": "KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-22013",
    "datePublished": "2025-04-08T08:18:04.000Z",
    "dateReserved": "2024-12-29T08:45:45.806Z",
    "dateUpdated": "2026-08-05T11:55:59.327Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-22013",
      "date": "2026-09-19",
      "epss": "0.00212",
      "percentile": "0.1181"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "arch/arm64/kernel/fpsimd.c",
                  "arch/arm64/kvm/fpsimd.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "5289ac43b69c61a49c75720921f2008005a31c43",
                    "status": "affected",
                    "version": "c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e",
                    "status": "affected",
                    "version": "d5f7d3833b534f9e43e548461dba1e60aa82f587",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "806d5c1e1d2e5502175a24bf70f251648d99c36a",
                    "status": "affected",
                    "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "79e140bba70bcacc5fe15bf8c0b958793fd7d56f",
                    "status": "affected",
                    "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "900b444be493b7f404898c785d6605b177a093d0",
                    "status": "affected",
                    "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "fbc7e61195e23f744814e78524b73b59faa54ab4",
                    "status": "affected",
                    "version": "93ae6b01bafee8fa385aa25ee7ebdb40057f6abe",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "arch/arm64/kernel/fpsimd.c",
                  "arch/arm64/kvm/fpsimd.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "6.2"
                  },
                  {
                    "lessThan": "6.2",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.6.*",
                    "status": "unaffected",
                    "version": "6.6.85",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.12.*",
                    "status": "unaffected",
                    "version": "6.12.21",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.13.*",
                    "status": "unaffected",
                    "version": "6.13.9",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "6.14",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "BCB56F36-C998-496A-A2E4-D9E0BB3A5BFC",
                    "versionEndExcluding": "6.6.85",
                    "versionStartIncluding": "6.2",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "3B63C450-D73B-4A53-9861-98E25C16E842",
                    "versionEndExcluding": "6.12.21",
                    "versionStartIncluding": "6.7",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "FAECBE4D-58CF-4836-BBAB-5E28B800A778",
                    "versionEndExcluding": "6.13.9",
                    "versionStartIncluding": "6.13",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:6.14:rc1:*:*:*:*:*:*",
                    "matchCriteriaId": "186716B6-2B66-4BD0-852E-D48E71C0C85F",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:linux:linux_kernel:6.14:rc2:*:*:*:*:*:*",
                    "matchCriteriaId": "0D3E781C-403A-498F-9DA9-ECEE50F41E75",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state\n\nThere are several problems with the way hyp code lazily saves the host\u0027s\nFPSIMD/SVE state, including:\n\n* Host SVE being discarded unexpectedly due to inconsistent\n  configuration of TIF_SVE and CPACR_ELx.ZEN. This has been seen to\n  result in QEMU crashes where SVE is used by memmove(), as reported by\n  Eric Auger:\n\n  https://issues.redhat.com/browse/RHEL-68997\n\n* Host SVE state is discarded *after* modification by ptrace, which was an\n  unintentional ptrace ABI change introduced with lazy discarding of SVE state.\n\n* The host FPMR value can be discarded when running a non-protected VM,\n  where FPMR support is not exposed to a VM, and that VM uses\n  FPSIMD/SVE. In these cases the hyp code does not save the host\u0027s FPMR\n  before unbinding the host\u0027s FPSIMD/SVE/SME state, leaving a stale\n  value in memory.\n\nAvoid these by eagerly saving and \"flushing\" the host\u0027s FPSIMD/SVE/SME\nstate when loading a vCPU such that KVM does not need to save any of the\nhost\u0027s FPSIMD/SVE/SME state. For clarity, fpsimd_kvm_prepare() is\nremoved and the necessary call to fpsimd_save_and_flush_cpu_state() is\nplaced in kvm_arch_vcpu_load_fp(). As \u0027fpsimd_state\u0027 and \u0027fpmr_ptr\u0027\nshould not be used, they are set to NULL; all uses of these will be\nremoved in subsequent patches.\n\nHistorical problems go back at least as far as v5.17, e.g. erroneous\nassumptions about TIF_SVE being clear in commit:\n\n  8383741ab2e773a9 (\"KVM: arm64: Get rid of host SVE tracking/saving\")\n\n... and so this eager save+flush probably needs to be backported to ALL\nstable trees."
          },
          {
            "lang": "es",
            "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: KVM: arm64: Guardar y vaciar incondicionalmente el estado FPSIMD/SVE/SME del host Hay varios problemas con la forma en que el c\u00f3digo hyp guarda de forma diferida el estado FPSIMD/SVE del host, incluidos: * El SVE del host se descarta inesperadamente debido a una configuraci\u00f3n inconsistente de TIF_SVE y CPACR_ELx.ZEN. Se ha visto que esto da como resultado fallos de QEMU donde memmove() usa SVE, como lo inform\u00f3 Eric Auger: https://issues.redhat.com/browse/RHEL-68997 * El estado SVE del host se descarta *despu\u00e9s* de la modificaci\u00f3n por ptrace, que fue un cambio de ABI de ptrace no intencionado introducido con el descarte diferido del estado SVE. * El valor FPMR del host se puede descartar cuando se ejecuta una VM no protegida, donde la compatibilidad con FPMR no est\u00e1 expuesta a una VM y esa VM usa FPSIMD/SVE. En estos casos, el c\u00f3digo hyp no guarda el FPMR del host antes de desvincular su estado FPSIMD/SVE/SME, lo que deja un valor obsoleto en memoria. Para evitar esto, guarde y vac\u00ede el estado FPSIMD/SVE/SME del host al cargar una vCPU, de modo que KVM no tenga que guardar ninguno de sus estados. Para mayor claridad, se ha eliminado fpsimd_kvm_prepare() y la llamada necesaria a fpsimd_save_and_flush_cpu_state() se ha ubicado en kvm_arch_vcpu_load_fp(). Dado que \u0027fpsimd_state\u0027 y \u0027fpmr_ptr\u0027 no deben usarse, se establecen en NULL; todos sus usos se eliminar\u00e1n en parches posteriores. Los problemas hist\u00f3ricos se remontan al menos a la versi\u00f3n v5.17, por ejemplo, suposiciones err\u00f3neas acerca de que TIF_SVE est\u00e1 claro en el commit: 8383741ab2e773a9 (\"KVM: arm64: deshacerse del seguimiento/guardado de SVE del host\")... y por eso, este ansioso guardado y vaciado probablemente deba ser retrotra\u00eddo a TODOS los \u00e1rboles estables."
          }
        ],
        "id": "CVE-2025-22013",
        "lastModified": "2026-07-30T06:22:03.057",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 7.3,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "LOW",
                "integrityImpact": "HIGH",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 5.5,
              "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
              "type": "Secondary"
            },
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 5.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2025-04-08T09:15:25.643",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/5289ac43b69c61a49c75720921f2008005a31c43"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56f"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36a"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "tags": [
              "Patch"
            ],
            "url": "https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "NVD-CWE-noinfo"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-07-30T09:37:46+00:00",
      "cve": "CVE-2025-22013",
      "id": "CVE-2025-22013",
      "initial_release_date": "2025-04-08T00:00:00+00:00",
      "product_status:fixed": "279",
      "product_status:known_affected": "184",
      "product_status:known_not_affected": "90",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: KVM: arm64: Unconditionally save+flush host FPSIMD/SVE/SME state",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-22013.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.


Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.