{
  "cveId": "CVE-2026-93815",
  "url": "https://patchblox.com/security/cve/CVE-2026-93815",
  "summary": "CVE-2026-93815 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-93815, released September 24, 2026. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "net: au1000: move free_irq out of the close-time spinlocked section",
  "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-\u003Elock 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-\u003Elock held across the MAC reset, queue stop and free_irq(dev-\u003Eirq, dev).  A directed runtime validation kept that ndo_stop carrier and the same free_irq(dev-\u003Eirq, dev) operation under the driver lock. Lockdep reported \u0022BUG: sleeping function called from invalid context\u0022 and \u0022Invalid wait context\u0022 while free_irq() was taking desc-\u003Erequest_mutex, with au1000_close() and free_irq() on the stack.  Drop aup-\u003Elock 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.",
  "published": "2026-09-24T17:17:15Z",
  "severity": "Moderate",
  "cvss": 4.1,
  "epss": 0.00173,
  "epssPercentile": 0.06702,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "vendorAdvisory": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-93815",
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.190-1",
      "fix": "DEBIAN-CVE-2026-93815",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-93815",
      "released": "2026-09-24T19:30:44Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.111-1",
      "fix": "DEBIAN-CVE-2026-93815",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-93815",
      "released": "2026-09-24T19:30:44Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "7.2.6-1",
      "fix": "DEBIAN-CVE-2026-93815",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-93815",
      "released": "2026-09-24T19:30:44Z"
    },
    {
      "platform": "linux",
      "product": "linux-6.12",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.12.111-1~deb12u1",
      "fix": "DEBIAN-CVE-2026-93815",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2026-93815",
      "released": "2026-09-24T19:30:44Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T13:31:49Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}