HighCVE-2025-22013

    Linux Kernel: security vulnerability (CVE-2025-22013)

    Published Last modified Sources: SUSE, BSI, CVE.org, EUVD

    Share

    What is affected, what to do

    Update Linux Kernel to version 6.6.85, Linux Kernel to version 6.12.21, Linux Kernel to version 6.13.9.

    Affected
    • Linux Kernel lt 6.2..6.6.85
    • Linux Kernel lt 6.7..6.12.21
    • Linux Kernel lt 6.13..6.13.9
    Fixed in
    • Linux Kernel 6.6.85
    • Linux Kernel 6.12.21
    • Linux Kernel 6.13.9
    • Linux Kernel 6.14

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.3

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    7.3

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: SUSE, BSI, CVE.org, EUVD

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 12.2

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    46.10 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.3 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.2 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    12.2
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 15 October 2026

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: suse_csaf, BSI WID Portal, BSI CSAF, cvelistv5, NVD (NIST), CVE.org (MITRE), ENISA EUVD

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • —
    • 6.2 – < 6.6.85
    • 6.7 – < 6.12.21
    • 6.13 – < 6.13.9
    • 6.14
    • 6.6.85
    • 6.12.21
    • 6.13.9
    SolarWindsSecurity Event Manager
    • < 2025.2.1
    • 2025.2.1

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxlinuxlinux_kernel6.14
    Linuxlinuxlinux_kernel—

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedLinux

      Show 18 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e
      Referenceadded
      —
      https://git.kernel.org/stable/c/5289ac43b69c61a49c75720921f2008005a31c43
      Referenceadded
      —
      https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56f
      Referenceadded
      —
      https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36a
      Referenceadded
      —
      https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0
      Referenceadded
      —
      https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4
      Referenceremoved
      https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e
      —
      Referenceremoved
      https://git.kernel.org/stable/c/5289ac43b69c61a49c75720921f2008005a31c43
      —
      Referenceremoved
      https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56f
      —
      Referenceremoved
      https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36a
      —
      Referenceremoved
      https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0
      —
      Referenceremoved
      https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/5289ac43b69c61a49c75720921f2008005a31c43 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/79e140bba70bcacc5fe15bf8c0b958793fd7d56f Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/806d5c1e1d2e5502175a24bf70f251648d99c36a Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/900b444be493b7f404898c785d6605b177a093d0 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/fbc7e61195e23f744814e78524b73b59faa54ab4 Types: Patch
      —

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2025-22013","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-15T21:44:00.434508Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. Record modifiedLinux

      CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-22013
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-22013"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-22013.svg?lang=en" alt="CVE-2025-22013 – NEOSEC Intel" height="20"></a>