CVE-2025-37901: irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs
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 GPIONOWAKEIRQ. 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 : mpmsettype+0x80/0xcc lr : mpmsettype+0x5c/0xcc Call trace: mpmsettype+0x80/0xcc (P) qcommpmsettype+0x64/0x158 irqchipsettypeparent+0x20/0x38 msmgpioirqsettype+0x50/0x530 irqsettrigger+0x60/0x184 setupirq+0x304/0x6bc requestthreadedirq+0xc8/0x19c edgedetectorsetup+0x260/0x364 linereqcreate+0x420/0x5a8 gpioioctl+0x2d4/0x6c0
Fix this by copying the check for GPIONOWAKEIRQ from qcom-pdc.c, so that MPM is removed entirely from the hierarchy for non-wake GPIOs.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In irqchip/qcom-mpm, update irq-qcom-mpm (mpm_set_type/irq handling path) to include the missing GPIO_NO_WAKE_IRQ check (copy the behavior from qcom-pdc.c). This prevents applying the IRQ domain hierarchy to GPIOs that are not wakeup capable and avoids crashes like 'Unable to handle kernel paging request' when handling non-wake GPIOs.
Linux kernel irqchip/qcom-mpm (irq-qcom-mpm) MPM IRQ domain hierarchy handling for non-wake GPIOs (GPIO_NO_WAKE_IRQ) = Add a check to copy the GPIO_NO_WAKE_IRQ guard logic from qcom-pdc.c so the hierarchy is explicitly disconnected for those non-wake GPIOs
Event History
Frequently Asked Questions
What is the severity of CVE-2025-37901?
CVE-2025-37901 is of medium severity, as it addresses potential system crashes in the Linux kernel when handling non-wake GPIOs.
How do I fix CVE-2025-37901?
To fix CVE-2025-37901, update your Qualcomm Linux kernel to the latest version that includes the patch for this vulnerability.
Which systems are affected by CVE-2025-37901?
CVE-2025-37901 affects Qualcomm Linux kernels, particularly those running on Snapdragon chipsets.
What type of vulnerability is CVE-2025-37901?
CVE-2025-37901 is a vulnerability in the Linux kernel related to the improper handling of non-wake GPIOs.
Can CVE-2025-37901 cause data loss?
While CVE-2025-37901 primarily risks system stability, there is a potential for data loss if the system crashes during critical operations.