CVE-2026-64428: gpio: sch: use raw_spinlock_t in the irq startup path
Published Jul 25, 2026
·Updated
gpio: sch: use rawspinlockt in the irq startup path
Affected Software
8 affected componentsFixes available
Linux Kernel
Microsoft azl3 kernel 6.6.144.1-1<6.6.145.2-1
6.6.145.2-1
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.145.2-1 - Configuration
In gpio: sch, use raw_spinlock_t for the controller lock in the irq startup path so that lock acquisitions in irqchip callbacks remain non-sleeping.
gpio: sch lock type = raw_spinlock_t
Event History
Jul 25, 2026
CVE Published
via MITRE·08:51 AM
Data Sourced
via MITRE·08:51 AM
Description
Data Sourced
via NVD·10:17 AM
RemedyDescriptionSeverityAffected Software
Jul 26, 2026
Data Sourced
via Microsoft·08:12 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:12 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-64428?
CVE-2026-64428 has a risk rating of 11, indicating a high severity vulnerability.
2
How do I fix CVE-2026-64428?
To resolve CVE-2026-64428, update the Linux kernel to a version that includes the patch for this vulnerability.
3
What components are affected by CVE-2026-64428?
CVE-2026-64428 affects the GPIO subsystem within the Linux kernel.
4
What type of vulnerability is CVE-2026-64428?
CVE-2026-64428 is categorized as a race condition vulnerability in the interrupt management path.
5
When was CVE-2026-64428 published?
CVE-2026-64428 was published on July 25, 2026.