net: au1000: move free_irq out of the close-time spinlocked section
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 26fd652915123a690f19d62b253b545a53f3cd51; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in e1b5a13249975fec3cf654efa84f57118db2da2c; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 4536667fba8ddbaff2f2a135080ae6aabf737b5e; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in fc2233f1ab2a1ca562869bca6987d7477671388c; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in f48763beab4eea41fc480c9702ec6eebe8d75e4f
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.271; From 5.11.0 · fixed in 5.15.222; From 5.16.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53
References 7
git.kernel.org
- stable/c/f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc
- stable/c/26fd652915123a690f19d62b253b545a53f3cd51
- stable/c/d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e
- stable/c/e1b5a13249975fec3cf654efa84f57118db2da2c
- stable/c/4536667fba8ddbaff2f2a135080ae6aabf737b5e
- stable/c/fc2233f1ab2a1ca562869bca6987d7477671388c
- stable/c/f48763beab4eea41fc480c9702ec6eebe8d75e4f