Answer in brief
CVE-2025-37901 records a Unknown severity vulnerability in irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.18 | Not reported |
| Linux/Linuxgeneric | >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <45aced97f01d5ab14c8a2a60f6748f18c501c3f5 || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <f102342360950b56959e5fff4a874ea88ae13758 || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <d5c10448f411a925dd59005785cb971f0626e032 || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <38a05c0b87833f5b188ae43b428b1f792df2b384 | 45aced97f01d5ab14c8a2a60f6748f18c501c3f5, dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf, f102342360950b56959e5fff4a874ea88ae13758, d5c10448f411a925dd59005785cb971f0626e032, 38a05c0b87833f5b188ae43b428b1f792df2b384 |
Published upstream
May 20, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-37901 records a Unknown severity vulnerability in irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 5.18 | Not reported |
| Linux/Linuxgeneric | >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <45aced97f01d5ab14c8a2a60f6748f18c501c3f5 || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <f102342360950b56959e5fff4a874ea88ae13758 || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <d5c10448f411a925dd59005785cb971f0626e032 || >=a6199bb514d8a63f61c2a22c1f912376e14d0fb2 <38a05c0b87833f5b188ae43b428b1f792df2b384 | 45aced97f01d5ab14c8a2a60f6748f18c501c3f5, dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf, f102342360950b56959e5fff4a874ea88ae13758, d5c10448f411a925dd59005785cb971f0626e032, 38a05c0b87833f5b188ae43b428b1f792df2b384 |
Published upstream
May 20, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.