CVE-2026-64428
Last modified
CVE-2026-64428 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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->lock with spin_lock_irqsave(). The callback can be reached from irq_startup() while setting up a requested IRQ. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
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->lock 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() -> __setup_irq() -> irq_startup() -> sch_irq_unmask() -> sch_irq_mask_unmask() carrier and used the original spin_lock_irqsave(&sch->lock) 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.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.13, < 5.15.212 |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 |
| Linux | Linux Kernel | >= 6.7, < 6.12.97 |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64428?
How severe is CVE-2026-64428?
How do I fix CVE-2026-64428?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64422In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64423In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64424In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64425In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64426In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64427In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64429In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-6443All plugins by Essentialplugin for WordPress are vulnerable …9.8
- CVE-2026-64430In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64431In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64432In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64433In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64428?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
