CVE-2024-50100

Vulnérabilité moyenne dans Linux (Linux)

CVSS 5.5 · Moyenne
EPSS 0.2%
Linux•Linux•Versions : 6.12, 6.11.5, <=*, <f828205ee3e4ddc712a13fba6c9902d51e91ddaf, <=6.11.*, 6.10, a7f3813e589fd8e2834720829a47b5eb914a9afe, <cf7ee2291da551fc4b109fda1f6a332cb8212065, <7d85884576a3be3616c260fc1fa862a59579d1ab, 0, 4a4cb56556124027f4846ff30849c0ede981aa92, <6.10, 8ffba8d917f44a8acbfccbdec331204353ac8ac8, <5189df7b8088268012882c220d6aca4e64981348

Description

In the Linux kernel, the following vulnerability has been resolved: USB: gadget: dummy-hcd: Fix "task hung" problem The syzbot fuzzer has been encountering "task hung" problems ever since the dummy-hcd driver was changed to use hrtimers instead of regular timers. It turns out that the problems are caused by a subtle difference between the timer_pending() and hrtimer_active() APIs. The changeover blindly replaced the first by the second. However, timer_pending() returns True when the timer is queued but not when its callback is running, whereas hrtimer_active() returns True when the hrtimer is queued _or_ its callback is running. This difference occasionally caused dummy_urb_enqueue() to think that the callback routine had not yet started when in fact it was almost finished. As a result the hrtimer was not restarted, which made it impossible for the driver to dequeue later the URB that was just enqueued. This caused usb_kill_urb() to hang, and things got worse from there. Since hrtimers have no API for telling when they are queued and the callback isn't running, the driver must keep track of this for itself. That's what this patch does, adding a new "timer_pending" flag and setting or clearing it at the appropriate times.

Gravité et risque d'exploitation

CVE-2024-50100 obtient un score CVSS de 5.5/10, soit une gravité moyenne. 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 13.5 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 6.12, 6.11.5, <=*, <f828205ee3e4ddc712a13fba6c9902d51e91ddaf, <=6.11.*, 6.10, a7f3813e589fd8e2834720829a47b5eb914a9afe, <cf7ee2291da551fc4b109fda1f6a332cb8212065, <7d85884576a3be3616c260fc1fa862a59579d1ab, 0, 4a4cb56556124027f4846ff30849c0ede981aa92, <6.10, 8ffba8d917f44a8acbfccbdec331204353ac8ac8, <5189df7b8088268012882c220d6aca4e64981348) 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