CVE-2026-93815net: au1000: move free_irq out of the close-time spinlocked section
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 9 days later
· 9 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 26fd652915123a690f19d62b253b545a53f3cd51
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e1b5a13249975fec3cf654efa84f57118db2da2c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 4536667fba8ddbaff2f2a135080ae6aabf737b5e
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < fc2233f1ab2a1ca562869bca6987d7477671388c
- affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < f48763beab4eea41fc480c9702ec6eebe8d75e4f
- affected 2.6.12
- unaffected < 2.6.12
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc (opens in a new tab)
- https://git.kernel.org/stable/c/26fd652915123a690f19d62b253b545a53f3cd51 (opens in a new tab)
- https://git.kernel.org/stable/c/d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e (opens in a new tab)
- https://git.kernel.org/stable/c/e1b5a13249975fec3cf654efa84f57118db2da2c (opens in a new tab)
- https://git.kernel.org/stable/c/4536667fba8ddbaff2f2a135080ae6aabf737b5e (opens in a new tab)
- https://git.kernel.org/stable/c/fc2233f1ab2a1ca562869bca6987d7477671388c (opens in a new tab)
- https://git.kernel.org/stable/c/f48763beab4eea41fc480c9702ec6eebe8d75e4f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86203 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-93815)Record last updated .