CVE-2025-38516

MEDIUM EPSS 4.5%
Published Aug 16, 202510mo ago · Modified Jun 17, 20261w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Aug 16, 2025 10mo ago
Last Modified Jun 17, 2026 1w ago

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.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
4.5% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-476 NULL Pointer Dereference Memory Safety

Affected Products 13

VendorProductVersionRange
linuxlinux_kernel*≥3.14  –  <5.4.296
linuxlinux_kernel*≥5.5  –  <5.10.240
linuxlinux_kernel*≥5.11  –  <5.15.189
linuxlinux_kernel*≥5.16  –  <6.1.146
linuxlinux_kernel*≥6.2  –  <6.6.99
linuxlinux_kernel*≥6.7  –  <6.12.39
linuxlinux_kernel*≥6.13  –  <6.15.7
linuxlinux_kernel6.16any
linuxlinux_kernel6.16any
linuxlinux_kernel6.16any
linuxlinux_kernel6.16any
linuxlinux_kernel6.16any
debiandebian_linux11.0any

References 10

  • git.kernel.org https://git.kernel.org/stable/c/1d57f7132662e96aace3b8a000616efde289aae1
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/275605a8b48002fe98675a5c06f3e39c09067ff2
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0a
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/6a89563ccf9cd0d745e2291302878a061508573f
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/93712205ce2f1fb047739494c0399a26ea4f0890
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/97c9c7daeeb00c6e1d5e84084041f79c2d2dce22
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/cb4b08a095b1fa4b3fca782757517e4e9a917d8e
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/cc145e02d6b8494c48f91958d52fa76b7e577f7b
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
    Mailing ListThird Party Advisory
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
    Mailing ListThird Party Advisory

Remediation

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