CVE-2026-93815
Last modified
CVE-2026-93815 is a vulnerability of currently unknown severity. 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.
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4536667fba8ddbaff2f2a135080ae6aabf737b5e; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < fc2233f1ab2a1ca562869bca6987d7477671388c; >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < f48763beab4eea41fc480c9702ec6eebe8d75e4f |
| Linux | Linux | 2.6.12 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-93815?
How severe is CVE-2026-93815?
How do I fix CVE-2026-93815?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-9381A vulnerability was detected in Edimax BR-6675nD 1.12. Affec…8.8
- CVE-2026-93810In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-93811In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93812In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93813In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-93814In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93816In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-93817In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-93818In the Linux kernel, the following vulnerability has been re…
- CVE-2026-93819In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9382A flaw has been found in Edimax BR-6675nD 1.12. Affected by …8.8
- CVE-2026-93820In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-93815?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
