Heimdall Security Logo

CVE-2026-93815

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

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, 2.6.12, 6.18.53, 0, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <4536667fba8ddbaff2f2a135080ae6aabf737b5e, 6.1.189, <d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e, <26fd652915123a690f19d62b253b545a53f3cd51, <fc2233f1ab2a1ca562869bca6987d7477671388c, <=6.18.*, 5.15.222, <e1b5a13249975fec3cf654efa84f57118db2da2c, <=*, <=5.15.*, <f48763beab4eea41fc480c9702ec6eebe8d75e4f, <f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc, 7.2, 6.12.111

Description

In the Linux kernel, the following vulnerability has been resolved: net: au1000: move free_irq out of the close-time spinlocked section au1000_close() calls free_irq() while aup->lock is still held with spin_lock_irqsave(). free_irq() can sleep because it takes the IRQ descriptor request mutex, so it does not belong inside the close-time spinlocked section. This was found by our static analysis tool and then confirmed by manual review of the in-tree au1000_close() .ndo_stop path. The reviewed path keeps aup->lock held across the MAC reset, queue stop and free_irq(dev->irq, dev). A directed runtime validation kept that ndo_stop carrier and the same free_irq(dev->irq, dev) operation under the driver lock. Lockdep reported "BUG: sleeping function called from invalid context" and "Invalid wait context" while free_irq() was taking desc->request_mutex, with au1000_close() and free_irq() on the stack. Drop aup->lock before freeing the IRQ. The protected close-time work still stops the device and queue before IRQ teardown, but the sleepable IRQ core path now runs outside the spinlocked section.

Gravité et risque d'exploitation

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

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 2.6.12, 6.18.53, 0, <2.6.12, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 5.10.271, 6.6.158, <=5.10.*, <=6.6.*, <4536667fba8ddbaff2f2a135080ae6aabf737b5e, 6.1.189, <d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e, <26fd652915123a690f19d62b253b545a53f3cd51, <fc2233f1ab2a1ca562869bca6987d7477671388c, <=6.18.*, 5.15.222, <e1b5a13249975fec3cf654efa84f57118db2da2c, <=*, <=5.15.*, <f48763beab4eea41fc480c9702ec6eebe8d75e4f, <f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc, 7.2, 6.12.111) 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