CVE-2025-38516: Linux kernel · pinctrl: qcom: msm: mark certain pins as invalid for interrupts
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cc145e02d6b8494c48f91958d52fa76b7e577f7b : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:19 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in cc145e02d6b8494c48f91958d52fa76b7e577f7b, cb4b08a095b1fa4b3fca782757517e4e9a917d8e, 93712205ce2f1fb047739494c0399a26ea4f0890 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 16 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: pinctrl: qcom: msm: mark certain pins as invalid for interrupts On some platforms, the UFS-reset pin has no interrupt logic in TLMM but is nevertheless registered as a GPIO in the kernel. This enables the user-space to trigger a BUG() in the pinctrl-msm driver by running, for example: `gpiomon -c 0 113` on RB2. The exact culprit is requesting pins whose intr_detection_width setting is not 1 or 2 for interrupts. This hits a BUG() in msm_gpio_irq_set_type(). Potentially crashing the kernel due to an invalid request from user-space is not optimal, so let's go through the pins and mark those that would fail the check as invalid for the irq chip as we should not even register them as available irqs. This function can be extended if we determine that there are more corner-cases like this.
References
- git.kernel.org/stable/c/6a89563ccf9cd0d745e2291302878a061508573f (opens in a new tab)
- git.kernel.org/stable/c/3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0a (opens in a new tab)
- git.kernel.org/stable/c/cb4b08a095b1fa4b3fca782757517e4e9a917d8e (opens in a new tab)
- git.kernel.org/stable/c/cc145e02d6b8494c48f91958d52fa76b7e577f7b (opens in a new tab)
- git.kernel.org/stable/c/1d57f7132662e96aace3b8a000616efde289aae1 (opens in a new tab)
- git.kernel.org/stable/c/275605a8b48002fe98675a5c06f3e39c09067ff2 (opens in a new tab)
- git.kernel.org/stable/c/97c9c7daeeb00c6e1d5e84084041f79c2d2dce22 (opens in a new tab)
- git.kernel.org/stable/c/93712205ce2f1fb047739494c0399a26ea4f0890 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html (opens in a new tab)