Heimdall Security Logo

CVE-2024-53135

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

CVSS 8.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : 6.12, <=6.1.*, <b8a1d572478b6f239061ee9578b2451bf2f021c2, <=6.11.*, <aa0d42cacf093a6fcca872edc954f6f812926a17, <b91bb0ce5cd7005b376eac690ec664c1b56372ec, 6.1.119, 0, <d28b059ee4779b5102c5da6e929762520510e406, 5.10.231, 5.15.174, 6.11.10, <d4b42f926adcce4e5ec193c714afd9d37bba8e5b, <=5.10.*, <=6.6.*, 5.0, 6.6.63, <=5.4.*, <5.0, <=*, <=5.15.*, 5.4.287, <e6716f4230a8784957273ddd27326264b27b9313, f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, <c3742319d021f5aa3a0a8c828485fee14753f6de

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN Hide KVM's pt_mode module param behind CONFIG_BROKEN, i.e. disable support for virtualizing Intel PT via guest/host mode unless BROKEN=y. There are myriad bugs in the implementation, some of which are fatal to the guest, and others which put the stability and health of the host at risk. For guest fatalities, the most glaring issue is that KVM fails to ensure tracing is disabled, and *stays* disabled prior to VM-Enter, which is necessary as hardware disallows loading (the guest's) RTIT_CTL if tracing is enabled (enforced via a VMX consistency check). Per the SDM: If the logical processor is operating with Intel PT enabled (if IA32_RTIT_CTL.TraceEn = 1) at the time of VM entry, the "load IA32_RTIT_CTL" VM-entry control must be 0. On the host side, KVM doesn't validate the guest CPUID configuration provided by userspace, and even worse, uses the guest configuration to decide what MSRs to save/load at VM-Enter and VM-Exit. E.g. configuring guest CPUID to enumerate more address ranges than are supported in hardware will result in KVM trying to passthrough, save, and load non-existent MSRs, which generates a variety of WARNs, ToPA ERRORs in the host, a potential deadlock, etc.

Gravité et risque d'exploitation

CVE-2024-53135 obtient un score CVSS de 8.8/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.24 %, ce qui la place devant 14.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12, <=6.1.*, <b8a1d572478b6f239061ee9578b2451bf2f021c2, <=6.11.*, <aa0d42cacf093a6fcca872edc954f6f812926a17, <b91bb0ce5cd7005b376eac690ec664c1b56372ec, 6.1.119, 0, <d28b059ee4779b5102c5da6e929762520510e406, 5.10.231, 5.15.174, 6.11.10, <d4b42f926adcce4e5ec193c714afd9d37bba8e5b, <=5.10.*, <=6.6.*, 5.0, 6.6.63, <=5.4.*, <5.0, <=*, <=5.15.*, 5.4.287, <e6716f4230a8784957273ddd27326264b27b9313, f99e3daf94ff35dd4a878d32ff66e1fd35223ad6, <c3742319d021f5aa3a0a8c828485fee14753f6de) 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