CVE-2026-93815 json
net: au1000: move free_irq out of the close-time spinlocked section
published 2026-09-24 46 d ago modified 2026-10-03 37 d ago also EUVD-2026-86203
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
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.
Patch / fix
- Linux Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.6-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-93815
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-93815
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc commit
- git.kernel.org/stable/c/26fd652915123a690f19d62b253b545a53f3cd51 commit
- git.kernel.org/stable/c/d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e commit
- git.kernel.org/stable/c/e1b5a13249975fec3cf654efa84f57118db2da2c commit
- git.kernel.org/stable/c/4536667fba8ddbaff2f2a135080ae6aabf737b5e commit
- git.kernel.org/stable/c/fc2233f1ab2a1ca562869bca6987d7477671388c commit
- git.kernel.org/stable/c/f48763beab4eea41fc480c9702ec6eebe8d75e4f commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-93815 updated cvss 5.5
kernel: net: au1000: move free_irq out of the close-time spinlocked section
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebc
- git.kernel.org /stable/c/26fd652915123a690f19d62b253b545a53f3cd51
- git.kernel.org /stable/c/d514b08ed61fdffe23604fd3e9e53c07cbe5ac3e
- git.kernel.org /stable/c/e1b5a13249975fec3cf654efa84f57118db2da2c
- git.kernel.org /stable/c/4536667fba8ddbaff2f2a135080ae6aabf737b5e
- git.kernel.org /stable/c/fc2233f1ab2a1ca562869bca6987d7477671388c
- git.kernel.org /stable/c/f48763beab4eea41fc480c9702ec6eebe8d75e4f
Sources
- CVE List CVE-2026-93815
- NVD CVE-2026-93815
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.