Kernel crash via premature GPIO IRQ access
Published Feb 26, 2025 · Updated May 23, 2026
A GPIO initialization race in the Linux kernel allows local users to crash the system by provoking an I2C device probe. The gpiochip_to_irq() path reads gc->irq.domain through the I2C interface before gpiochip_add_irqchip() finishes initializing the IRQ chip, so a competing probe dereferences NULL. Exploitation requires local low-privileged access and a susceptible GPIO/I2C initialization sequence; the reported consequence is a kernel crash.
Summary
What happened
A GPIO initialization race in the Linux kernel allows local users to crash the system by provoking an I2C device probe. The gpiochip_to_irq() path reads gc->irq.domain through the I2C interface before gpiochip_add_irqchip() finishes initializing the IRQ chip, so a competing probe dereferences NULL. Exploitation requires local low-privileged access and a susceptible GPIO/I2C initialization sequence; the reported consequence is a kernel crash.
The record
- CVE
- CVE-2022-49072
- Published
- Feb 26, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=44dfa46aaf7cf594ac89bc1a0c0e56c498b31269
- Affected versionversion=48057ed1840fde9239b1e000bea1a0a1f07c5e99 <0912cf021fb5749372b3782611d8b1de4986c13a
- Affected versionversion=48057ed1840fde9239b1e000bea1a0a1f07c5e99 <2c1fa3614795e2b24da1ba95de0b27b8f6ea4537
- Affected versionversion=48057ed1840fde9239b1e000bea1a0a1f07c5e99 <5467801f1fcbdc46bc7298a84dbf3ca1ff2a7320
- Affected versionversion=48057ed1840fde9239b1e000bea1a0a1f07c5e99 <7e88a50704b0c49ad3f2d11e8b963341cf68a89f
- Affected versionversion=48057ed1840fde9239b1e000bea1a0a1f07c5e99 <f8dea54f74cae8c2e4d7b2952e8fed7743a85c87
- Affected versionversion=5.2.14 <5.3
- Affected versionversion=5.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo