Heimdall Security Logo

CVE-2025-37875

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.3%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <=6.14.*, <31959e06143692f7e02b8eef7d7d6ac645637906, 0, <=6.6.*, <f3516229cd12dcd45f23ed01adab17e8772b1bd5, <5.15, 6.12.25, 6.1.135, <c1f174edaccc5a00f8e218c42a0aa9156efd5f76, 5.15, <0c03e4fbe1321697d9d04587e21e416705e1b19f, 6.15, <=*, <=5.15.*, 5.15.181, 6.14.4, <16194ca3f3b4448a062650c869a7b3b206c6f5d3, <8e404ad95d2c10c261e2ef6992c7c12dde03df0e, a90ec84837325df4b9a6798c2cc0df202b5680bd, 6.6.88

Description

In the Linux kernel, the following vulnerability has been resolved: igc: fix PTM cycle trigger logic Writing to clear the PTM status 'valid' bit while the PTM cycle is triggered results in unreliable PTM operation. To fix this, clear the PTM 'trigger' and status after each PTM transaction. The issue can be reproduced with the following: $ sudo phc2sys -R 1000 -O 0 -i tsn0 -m Note: 1000 Hz (-R 1000) is unrealistically large, but provides a way to quickly reproduce the issue. PHC2SYS exits with: "ioctl PTP_OFFSET_PRECISE: Connection timed out" when the PTM transaction fails This patch also fixes a hang in igc_probe() when loading the igc driver in the kdump kernel on systems supporting PTM. The igc driver running in the base kernel enables PTM trigger in igc_probe(). Therefore the driver is always in PTM trigger mode, except in brief periods when manually triggering a PTM cycle. When a crash occurs, the NIC is reset while PTM trigger is enabled. Due to a hardware problem, the NIC is subsequently in a bad busmaster state and doesn't handle register reads/writes. When running igc_probe() in the kdump kernel, the first register access to a NIC register hangs driver probing and ultimately breaks kdump. With this patch, igc has PTM trigger disabled most of the time, and the trigger is only enabled for very brief (10 - 100 us) periods when manually triggering a PTM cycle. Chances that a crash occurs during a PTM trigger are not 0, but extremely reduced.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <=6.14.*, <31959e06143692f7e02b8eef7d7d6ac645637906, 0, <=6.6.*, <f3516229cd12dcd45f23ed01adab17e8772b1bd5, <5.15, 6.12.25, 6.1.135, <c1f174edaccc5a00f8e218c42a0aa9156efd5f76, 5.15, <0c03e4fbe1321697d9d04587e21e416705e1b19f, 6.15, <=*, <=5.15.*, 5.15.181, 6.14.4, <16194ca3f3b4448a062650c869a7b3b206c6f5d3, <8e404ad95d2c10c261e2ef6992c7c12dde03df0e, a90ec84837325df4b9a6798c2cc0df202b5680bd, 6.6.88) 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