Kernel crash via unsupported GPIO interrupt request
Published Aug 16, 2025 · Updated May 11, 2026
Denial of service in the Linux Qualcomm MSM pin controller allows local users to crash the kernel through an invalid GPIO interrupt request. The driver registers certain UFS-reset GPIO pins as interrupt-capable even when their intr_detection_width is neither 1 nor 2, so msm_gpio_irq_set_type() reaches a BUG(). Low-privileged local access to an affected Qualcomm platform is required, and triggering the flaw interrupts the entire system.
Summary
What happened
Denial of service in the Linux Qualcomm MSM pin controller allows local users to crash the kernel through an invalid GPIO interrupt request. The driver registers certain UFS-reset GPIO pins as interrupt-capable even when their intr_detection_width is neither 1 nor 2, so msm_gpio_irq_set_type() reaches a BUG(). Low-privileged local access to an affected Qualcomm platform is required, and triggering the flaw interrupts the entire system.
The record
- CVE
- CVE-2025-38516
- Published
- Aug 16, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 16, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=3.14
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <1d57f7132662e96aace3b8a000616efde289aae1
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <275605a8b48002fe98675a5c06f3e39c09067ff2
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0a
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <6a89563ccf9cd0d745e2291302878a061508573f
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <93712205ce2f1fb047739494c0399a26ea4f0890
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <97c9c7daeeb00c6e1d5e84084041f79c2d2dce22
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <cb4b08a095b1fa4b3fca782757517e4e9a917d8e
- Affected versionversion=f365be0925729508fd8e62f8bdb504ef896cb6e0 <cc145e02d6b8494c48f91958d52fa76b7e577f7b
What conditions does exploitation require?
What is affected?
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
- gpiomon unsupported-pin interrupt triggerproof of concept · demonstrated
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