Heimdall Security Logo

CVE-2025-39801

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <3.2, <=6.12.*, <dfe40159eec6ca63b40133bfa783eee2e3ed829f, 6.12.44, <=6.16.*, 6.17, 0, 6.6.103, <f49697dfba2915a9ff36f94604eb76fa61413929, <=6.6.*, 72246da40f3719af3bfd104a2365b32537c27d83, 5.15.190, 3.2, <45eae113dccaf8e502090ecf5b3d9e9b805add6f, 6.1.149, <5a1a847d841505dba2bd85602daf5c218e1d85b8, <=*, <=5.15.*, <84c95dbf5bece56086cdb65a64162af35158bdd9, <db27482b9db340402e05d4e9b75352bbaca51af2, 6.16.4

Description

In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Remove WARN_ON for device endpoint command timeouts This commit addresses a rarely observed endpoint command timeout which causes kernel panic due to warn when 'panic_on_warn' is enabled and unnecessary call trace prints when 'panic_on_warn' is disabled. It is seen during fast software-controlled connect/disconnect testcases. The following is one such endpoint command timeout that we observed: 1. Connect ======= ->dwc3_thread_interrupt ->dwc3_ep0_interrupt ->configfs_composite_setup ->composite_setup ->usb_ep_queue ->dwc3_gadget_ep0_queue ->__dwc3_gadget_ep0_queue ->__dwc3_ep0_do_control_data ->dwc3_send_gadget_ep_cmd 2. Disconnect ========== ->dwc3_thread_interrupt ->dwc3_gadget_disconnect_interrupt ->dwc3_ep0_reset_state ->dwc3_ep0_end_control_data ->dwc3_send_gadget_ep_cmd In the issue scenario, in Exynos platforms, we observed that control transfers for the previous connect have not yet been completed and end transfer command sent as a part of the disconnect sequence and processing of USB_ENDPOINT_HALT feature request from the host timeout. This maybe an expected scenario since the controller is processing EP commands sent as a part of the previous connect. It maybe better to remove WARN_ON in all places where device endpoint commands are sent to avoid unnecessary kernel panic due to warn.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <3.2, <=6.12.*, <dfe40159eec6ca63b40133bfa783eee2e3ed829f, 6.12.44, <=6.16.*, 6.17, 0, 6.6.103, <f49697dfba2915a9ff36f94604eb76fa61413929, <=6.6.*, 72246da40f3719af3bfd104a2365b32537c27d83, 5.15.190, 3.2, <45eae113dccaf8e502090ecf5b3d9e9b805add6f, 6.1.149, <5a1a847d841505dba2bd85602daf5c218e1d85b8, <=*, <=5.15.*, <84c95dbf5bece56086cdb65a64162af35158bdd9, <db27482b9db340402e05d4e9b75352bbaca51af2, 6.16.4) 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