CVE-2025-38516
Last modified
CVE-2025-38516 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.14, < 5.4.296 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.240 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.189 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.146 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.99 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.39 | — |
| Linux | Linux Kernel | >= 6.13, < 6.15.7 | — |
| Linux | Linux Kernel | 6.16 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlMailing List, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlMailing List, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-38516?
How severe is CVE-2025-38516?
How do I fix CVE-2025-38516?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38510In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38511In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38512In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38513In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38514In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38515In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38517In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38518In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38519In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3852The WPshop 2 – E-Commerce plugin for WordPress is vulnerable…8.8
- CVE-2025-38520In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38521In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2025-38516?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
