Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38516, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < 6a89563ccf9cd0d745e2291302878a061508573f
    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < 3f8fc02c2582c1dfad1785e9c7bc8b4e1521af0a
    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < cb4b08a095b1fa4b3fca782757517e4e9a917d8e
    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < cc145e02d6b8494c48f91958d52fa76b7e577f7b
    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < 1d57f7132662e96aace3b8a000616efde289aae1
    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < 275605a8b48002fe98675a5c06f3e39c09067ff2
    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < 97c9c7daeeb00c6e1d5e84084041f79c2d2dce22
    • affected f365be0925729508fd8e62f8bdb504ef896cb6e0 – < 93712205ce2f1fb047739494c0399a26ea4f0890
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • unaffected 5.4.296 – ≤ 5.4.*
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.189 – ≤ 5.15.*
    • unaffected 6.1.146 – ≤ 6.1.*
    • unaffected 6.6.99 – ≤ 6.6.*
    • unaffected 6.12.39 – ≤ 6.12.*
    • unaffected 6.15.7 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38516 badge
[![CVE-2025-38516](https://cveledger.app/badge/CVE-2025-38516.svg)](https://cveledger.app/cve/CVE-2025-38516)

Record last updated .