Skip to content
Sign in Sign up
JA EN FR
SecPulse
High 7.3

Vulnerability in Linux kernel

CVE-2025-22013 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-22013 has been found in Linux kernel.
Data can be tampered with by attackers. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2025-22013" on the vendor's site.

CVE-2025-22013 (Linux kernel) — CVSS v3 7.3
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (unclassified) exists in Linux kernel.

Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

Severity

Severity: High (CVSS 7.3/10). Data can be tampered with by attackers.

How to fix

Update to the patched release per vendor advisory.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Linux Kernel
≥ 6.2.0, < 6.6.85
≥ 6.7.0, < 6.12.21
≥ 6.13.0, < 6.13.9
6.6.85
6.12.21
6.13.9

Fix status by distribution

Fixed packages published by each distribution for this CVE

Original description The description as published by the source.

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…

Source: NIST National Vulnerability Database NVD

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details