Skip to content
Threat Brief

← All advisories

CVE-2026-93815

Severity unknownNo known exploitationFix available

net: au1000: move free_irq out of the close-time spinlocked section

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 7% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before f48763beab4eea41fc480c9702ec6eebe8d75e4ff48763beab4eea41fc480c9702ec6eebe8d75e4fCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before f86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebcf86bca5b7857b85bfa8afdb4fa895d7c0a3f7ebcCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 26fd652915123a690f19d62b253b545a53f3cd5126fd652915123a690f19d62b253b545a53f3cd51CVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before d514b08ed61fdffe23604fd3e9e53c07cbe5ac3ed514b08ed61fdffe23604fd3e9e53c07cbe5ac3eCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before e1b5a13249975fec3cf654efa84f57118db2da2ce1b5a13249975fec3cf654efa84f57118db2da2cCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before 4536667fba8ddbaff2f2a135080ae6aabf737b5e4536667fba8ddbaff2f2a135080ae6aabf737b5eCVE Program
LinuxLinuxfrom 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 before fc2233f1ab2a1ca562869bca6987d7477671388cfc2233f1ab2a1ca562869bca6987d7477671388cCVE Program
LinuxLinux2.6.12Not documentedCVE Program
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 5.10.271 up to and including 5.10.*Not documentedCVE Program
LinuxLinux (unaffected)from 5.15.222 up to and including 5.15.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.1.189 up to and including 6.1.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.111 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.53 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.6.158 up to and including 6.6.*Not documentedCVE Program
LinuxLinux (unaffected)7.2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 2.6.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references