CVE-2026-98765

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 4.1.46, <=6.12.*, <4.2, a867d5b932ac4911d3f8a1e63505061b0c81f889, 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81, 4.4.92, 0, <4.10, 8590bc1da625dd4a589eac0fc3aa3cf4f400424d, 7.2.10, <3.3, e39b17143a5b5aac81f066d455e5d3a9877eb3ae, 4.9.55, <4.5, 4.13.6, <b263ff9b0fc5c1f371d65c4eb196b31263d039ff, <=6.18.*, <5298c96bf0068f3160969f7ddad81976d01a9b66, <7ce4dca0d53b1c3cb2b7e7bb2e42bf5db860caf2, <=7.2.*, 6.12.113, <=*, e84b4a008365b7edbd842a063ae28d040a98db25, <4.14, 7b416b9dac6ede26d4ca0c1a88b448b543623ff3, 3.16.52, 6.18.56, <3070806a7bc7bb36ed04a21022c09dafcc5619f4, <3.17, 4f8ae1fcb0dfbb72a7678f81bf01fb7fc85c6715, 3.2.97, 4.14, 7.3

Description

In the Linux kernel, the following vulnerability has been resolved: USB: gadget: dummy-hcd: Fix wait for outstanding request completions The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held). This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called. This is an oversight. Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback. If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running. Fix the oversight by incrementing the callback_usage value across request completion callbacks.

Gravité et risque d'exploitation

CVE-2026-98765 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.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 4.1.46, <=6.12.*, <4.2, a867d5b932ac4911d3f8a1e63505061b0c81f889, 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81, 4.4.92, 0, <4.10, 8590bc1da625dd4a589eac0fc3aa3cf4f400424d, 7.2.10, <3.3, e39b17143a5b5aac81f066d455e5d3a9877eb3ae, 4.9.55, <4.5, 4.13.6, <b263ff9b0fc5c1f371d65c4eb196b31263d039ff, <=6.18.*, <5298c96bf0068f3160969f7ddad81976d01a9b66, <7ce4dca0d53b1c3cb2b7e7bb2e42bf5db860caf2, <=7.2.*, 6.12.113, <=*, e84b4a008365b7edbd842a063ae28d040a98db25, <4.14, 7b416b9dac6ede26d4ca0c1a88b448b543623ff3, 3.16.52, 6.18.56, <3070806a7bc7bb36ed04a21022c09dafcc5619f4, <3.17, 4f8ae1fcb0dfbb72a7678f81bf01fb7fc85c6715, 3.2.97, 4.14, 7.3) 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