Heimdall Security Logo

CVE-2025-22013

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.3 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <fbc7e61195e23f744814e78524b73b59faa54ab4, <=6.12.*, 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, 6.13.9, 0, 6.14, <=6.6.*, 6.12.21, <04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e, <5289ac43b69c61a49c75720921f2008005a31c43, <79e140bba70bcacc5fe15bf8c0b958793fd7d56f, <900b444be493b7f404898c785d6605b177a093d0, d5f7d3833b534f9e43e548461dba1e60aa82f587, <6.2, 6.6.85, <806d5c1e1d2e5502175a24bf70f251648d99c36a, <=*, c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90, <=6.13.*, 6.2

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.

Gravité et risque d'exploitation

CVE-2025-22013 obtient un score CVSS de 7.3/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 10.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <fbc7e61195e23f744814e78524b73b59faa54ab4, <=6.12.*, 93ae6b01bafee8fa385aa25ee7ebdb40057f6abe, 6.13.9, 0, 6.14, <=6.6.*, 6.12.21, <04c50cc23a492c4d43fdaefc7c1ecc0ff6f7b82e, <5289ac43b69c61a49c75720921f2008005a31c43, <79e140bba70bcacc5fe15bf8c0b958793fd7d56f, <900b444be493b7f404898c785d6605b177a093d0, d5f7d3833b534f9e43e548461dba1e60aa82f587, <6.2, 6.6.85, <806d5c1e1d2e5502175a24bf70f251648d99c36a, <=*, c4ab60a86c5ed7c0d727c6dc8cec352e16bc7f90, <=6.13.*, 6.2) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE