{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.180-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.100-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.4-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux-6.12"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.100-1~deb12u1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  gpio: sch: use raw_spinlock_t in the irq startup path  sch_irq_unmask() enables the GPIO IRQ and then updates the controller state through sch_irq_mask_unmask(), which takes sch-\u003elock with spin_lock_irqsave().  The callback can be reached from irq_startup() while setting up a requested IRQ.  That path is not sleepable, but on PREEMPT_RT a regular spinlock_t becomes a sleeping lock.  This issue was found by our static analysis tool and then manually reviewed against the current tree.  The grounded PoC kept the request_threaded_irq() -\u003e __setup_irq() -\u003e irq_startup() -\u003e sch_irq_unmask() -\u003e sch_irq_mask_unmask() carrier and used the original spin_lock_irqsave(\u0026sch-\u003elock) edge.  Lockdep reported:    BUG: sleeping function called from invalid context   hardirqs last disabled at ... __setup_irq.constprop.0 ... [vuln_msv]   sch_rt_spin_lock_irqsave+0x1c/0x30 [vuln_msv]   sch_irq_mask_unmask.constprop.0+0x31/0x70 [vuln_msv]   __setup_irq.constprop.0+0xd/0x30 [vuln_msv]  Convert the SCH controller lock to raw_spinlock_t.  The same lock is also used by the GPIO direction and value callbacks, but those critical sections only update MMIO-backed GPIO registers and do not contain sleepable operations.  Keeping this register lock non-sleeping is therefore appropriate for the irqchip callbacks and does not change the GPIO-side locking contract.",
  "id": "DEBIAN-CVE-2026-64428",
  "modified": "2026-09-14T16:47:40.443619251Z",
  "published": "2026-07-25T10:17:26.947Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-64428"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-64428"
  ]
}