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-37901irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs

Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs On Qualcomm chipsets not all GPIOs are wakeup capable. Those GPIOs do not have a corresponding MPM pin and should not be handled inside the MPM driver. The IRQ domain hierarchy is always applied, so it's required to explicitly disconnect the hierarchy for those. The pinctrl-msm driver marks these with GPIO_NO_WAKE_IRQ. qcom-pdc has a check for this, but irq-qcom-mpm is currently missing the check. This is causing crashes when setting up interrupts for non-wake GPIOs: root@rb1:~# gpiomon -c gpiochip1 10 irq: IRQ159: trimming hierarchy from :soc@0:interrupt-controller@f200000-1 Unable to handle kernel paging request at virtual address ffff8000a1dc3820 Hardware name: Qualcomm Technologies, Inc. Robotics RB1 (DT) pc : mpm_set_type+0x80/0xcc lr : mpm_set_type+0x5c/0xcc Call trace: mpm_set_type+0x80/0xcc (P) qcom_mpm_set_type+0x64/0x158 irq_chip_set_type_parent+0x20/0x38 msm_gpio_irq_set_type+0x50/0x530 __irq_set_trigger+0x60/0x184 __setup_irq+0x304/0x6bc request_threaded_irq+0xc8/0x19c edge_detector_setup+0x260/0x364 linereq_create+0x420/0x5a8 gpio_ioctl+0x2d4/0x6c0 Fix this by copying the check for GPIO_NO_WAKE_IRQ from qcom-pdc.c, so that MPM is removed entirely from the hierarchy for non-wake GPIOs.

Timeline

  1. ID reserved

    By Linux

  2. · 34 days 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-37901, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.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.21% · top 88% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected a6199bb514d8a63f61c2a22c1f912376e14d0fb2 – < 45aced97f01d5ab14c8a2a60f6748f18c501c3f5
    • affected a6199bb514d8a63f61c2a22c1f912376e14d0fb2 – < dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf
    • affected a6199bb514d8a63f61c2a22c1f912376e14d0fb2 – < f102342360950b56959e5fff4a874ea88ae13758
    • affected a6199bb514d8a63f61c2a22c1f912376e14d0fb2 – < d5c10448f411a925dd59005785cb971f0626e032
    • affected a6199bb514d8a63f61c2a22c1f912376e14d0fb2 – < 38a05c0b87833f5b188ae43b428b1f792df2b384
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.138 – ≤ 6.1.*
    • unaffected 6.6.90 – ≤ 6.6.*
    • unaffected 6.12.28 – ≤ 6.12.*
    • unaffected 6.14.6 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .