CVE-2024-26934

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 6.9, <=6.1.*, 0, 5.15.154, 6.8.3, 4.4, <=5.10.*, <80ba43e9f799cbdd83842fc27db667289b3150f5, <=6.6.*, 5.10.215, <dbdf66250d2d33e8b27352fcb901de79f3521057, <ab062fa3dc69aea88fe62162c5881ba14b50ecc5, <12d6a5681a0a5cecc2af7860f0a1613fa7c6e947, <=5.4.*, <8cbdd324b41528994027128207fae8100dff094f, <1b175bc579f46520b11ecda443bcd2ee4904f66a, <e451709573f8be904a8a72d0775bf114d7c291d9, 4.19.312, <=4.19.*, 5.4.274, <=6.8.*, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 6.7.12, <07acf979da33c721357ff27129edf74c23c036c6, <=*, <=5.15.*, <=6.7.*, <122a06f1068bf5e39089863f4f60b1f5d4273384, 6.1.84, 6.6.24, <4.4

Description

In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in usb_deauthorize_interface() Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface's parent USB device. The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can't complete until the device lock has been released, and the lock won't be released until the removal has finished. The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback. Reported-and-tested by: Yue Sun <samsun1006219@gmail.com> Reported by: xingwei lee <xrivendell7@gmail.com>

Gravité et risque d'exploitation

CVE-2024-26934 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.19 %, ce qui la place devant 8.1 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.9, <=6.1.*, 0, 5.15.154, 6.8.3, 4.4, <=5.10.*, <80ba43e9f799cbdd83842fc27db667289b3150f5, <=6.6.*, 5.10.215, <dbdf66250d2d33e8b27352fcb901de79f3521057, <ab062fa3dc69aea88fe62162c5881ba14b50ecc5, <12d6a5681a0a5cecc2af7860f0a1613fa7c6e947, <=5.4.*, <8cbdd324b41528994027128207fae8100dff094f, <1b175bc579f46520b11ecda443bcd2ee4904f66a, <e451709573f8be904a8a72d0775bf114d7c291d9, 4.19.312, <=4.19.*, 5.4.274, <=6.8.*, 310d2b4124c073a2057ef9d952d4d938e9b1dfd9, 6.7.12, <07acf979da33c721357ff27129edf74c23c036c6, <=*, <=5.15.*, <=6.7.*, <122a06f1068bf5e39089863f4f60b1f5d4273384, 6.1.84, 6.6.24, <4.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