CVE-2025-38376

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.15.*, <937f49be49d6ee696eb5457c21ff89c135c9b5ae, 6.6.97, <=6.12.*, 6.16, <=*, <5fd585fedb79bac2af9976b0fa3ffa354f0cc0bb, 6.15.6, <31a6afbe86e8e9deba9ab53876ec49eafc7fd901, <6.2, <=6.6.*, 0, 235ffc17d0146d806f6ad8c094c24ff4878f2edb, <c68a27bbebbdb4e0ccd45d4f0df7111a09ddac24, 6.2, 6.12.37

Description

In the Linux kernel, the following vulnerability has been resolved: usb: chipidea: udc: disconnect/reconnect from host when do suspend/resume Shawn and John reported a hang issue during system suspend as below: - USB gadget is enabled as Ethernet - There is data transfer over USB Ethernet (scp a big file between host and device) - Device is going in/out suspend (echo mem > /sys/power/state) The root cause is the USB device controller is suspended but the USB bus is still active which caused the USB host continues to transfer data with device and the device continues to queue USB requests (in this case, a delayed TCP ACK packet trigger the issue) after controller is suspended, however the USB controller clock is already gated off. Then if udc driver access registers after that point, the system will hang. The correct way to avoid such issue is to disconnect device from host when the USB bus is not at suspend state. Then the host will receive disconnect event and stop data transfer in time. To continue make USB gadget device work after system resume, this will reconnect device automatically. To make usb wakeup work if USB bus is already at suspend state, this will keep connection for it only when USB device controller has enabled wakeup capability.

Gravité et risque d'exploitation

CVE-2025-38376 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.17 %, ce qui la place devant 5.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.15.*, <937f49be49d6ee696eb5457c21ff89c135c9b5ae, 6.6.97, <=6.12.*, 6.16, <=*, <5fd585fedb79bac2af9976b0fa3ffa354f0cc0bb, 6.15.6, <31a6afbe86e8e9deba9ab53876ec49eafc7fd901, <6.2, <=6.6.*, 0, 235ffc17d0146d806f6ad8c094c24ff4878f2edb, <c68a27bbebbdb4e0ccd45d4f0df7111a09ddac24, 6.2, 6.12.37) 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