{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-37901","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-04-16T04:51:23.965Z","datePublished":"2025-05-20T15:21:36.062Z","dateUpdated":"2026-08-05T11:58:11.172Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T11:58:11.172Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs\n\nOn Qualcomm chipsets not all GPIOs are wakeup capable. Those GPIOs do not\nhave a corresponding MPM pin and should not be handled inside the MPM\ndriver. The IRQ domain hierarchy is always applied, so it's required to\nexplicitly disconnect the hierarchy for those. The pinctrl-msm driver marks\nthese with GPIO_NO_WAKE_IRQ. qcom-pdc has a check for this, but\nirq-qcom-mpm is currently missing the check. This is causing crashes when\nsetting up interrupts for non-wake GPIOs:\n\n root@rb1:~# gpiomon -c gpiochip1 10\n   irq: IRQ159: trimming hierarchy from :soc@0:interrupt-controller@f200000-1\n   Unable to handle kernel paging request at virtual address ffff8000a1dc3820\n   Hardware name: Qualcomm Technologies, Inc. Robotics RB1 (DT)\n   pc : mpm_set_type+0x80/0xcc\n   lr : mpm_set_type+0x5c/0xcc\n   Call trace:\n    mpm_set_type+0x80/0xcc (P)\n    qcom_mpm_set_type+0x64/0x158\n    irq_chip_set_type_parent+0x20/0x38\n    msm_gpio_irq_set_type+0x50/0x530\n    __irq_set_trigger+0x60/0x184\n    __setup_irq+0x304/0x6bc\n    request_threaded_irq+0xc8/0x19c\n    edge_detector_setup+0x260/0x364\n    linereq_create+0x420/0x5a8\n    gpio_ioctl+0x2d4/0x6c0\n\nFix this by copying the check for GPIO_NO_WAKE_IRQ from qcom-pdc.c, so that\nMPM is removed entirely from the hierarchy for non-wake GPIOs."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The vulnerability is reached through the GPIO character device ioctl path (`gpio_ioctl` → `linereq_create` → `edge_detector_setup` → `request_threaded_irq`), or equivalently the legacy sysfs `edge` attribute, both of which require local access to the system. There is no network or adjacent-network path to `qcom_mpm_set_type()`.\nAC:L - Triggering is fully deterministic — a single `gpiomon -c gpiochipN <line>` on any GPIO absent from the SoC's `wakeirq_map` reliably reaches the out-of-bounds access, and non-wake lines are the majority on these SoCs and are trivially enumerable. No race, no memory-layout condition outside the attacker's control is needed for the corruption/crash.\nPR:L - The attacker only needs open access to `/dev/gpiochipN`, which on the embedded, robotics and IoT platforms that actually ship Qualcomm MPM is routinely granted to an unprivileged `gpio`-group account or service user via standard udev rules (0660 root:gpio) so that libgpiod consumers can run without root. No capability check exists anywhere along the path once the device node is opened.\nUI:N - The attacker performs the ioctl themselves in a single step; no victim action, configuration change, or interaction from another user is required.\nS:U - The out-of-bounds access corrupts kernel memory within the same security authority; there is no VM, IOMMU, or sandbox boundary crossed.\nC:H - `__assign_bit(0xFFFFFFFF, &val, ...)` performs a read-modify-write 511 MB beyond a kernel stack local, i.e. an unbounded out-of-bounds read of an arbitrary vmalloc-region word; combined with the accompanying write primitive this constitutes memory corruption that can be leveraged to disclose kernel memory.\nI:H - This is an out-of-bounds write: bit 63 of the unsigned long at a fixed +0x1FFFFFF8 offset from the kernel stack is set or cleared under attacker control (via the EDGE_RISING/EDGE_FALLING line flags), repeatably. With vmap'd stacks and vmalloc grooming, flipping the top bit of a pointer, length, or refcount in a neighbouring object is a real control-flow-corruption primitive.\nA:H - The reported and reproducible outcome is a kernel paging fault (\"Unable to handle kernel paging request\") in `mpm_set_type`, an oops taken inside `raw_spin_lock_irqsave(&priv->lock)` with interrupts disabled — so `priv->lock` is orphaned and all later MPM operations, including the wake handler and the suspend path, deadlock."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/irqchip/irq-qcom-mpm.c"],"versions":[{"version":"a6199bb514d8a63f61c2a22c1f912376e14d0fb2","lessThan":"45aced97f01d5ab14c8a2a60f6748f18c501c3f5","status":"affected","versionType":"git"},{"version":"a6199bb514d8a63f61c2a22c1f912376e14d0fb2","lessThan":"dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf","status":"affected","versionType":"git"},{"version":"a6199bb514d8a63f61c2a22c1f912376e14d0fb2","lessThan":"f102342360950b56959e5fff4a874ea88ae13758","status":"affected","versionType":"git"},{"version":"a6199bb514d8a63f61c2a22c1f912376e14d0fb2","lessThan":"d5c10448f411a925dd59005785cb971f0626e032","status":"affected","versionType":"git"},{"version":"a6199bb514d8a63f61c2a22c1f912376e14d0fb2","lessThan":"38a05c0b87833f5b188ae43b428b1f792df2b384","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/irqchip/irq-qcom-mpm.c"],"versions":[{"version":"5.18","status":"affected"},{"version":"0","lessThan":"5.18","status":"unaffected","versionType":"semver"},{"version":"6.1.138","lessThanOrEqual":"6.1.*","status":"unaffected","versionType":"semver"},{"version":"6.6.90","lessThanOrEqual":"6.6.*","status":"unaffected","versionType":"semver"},{"version":"6.12.28","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.14.6","lessThanOrEqual":"6.14.*","status":"unaffected","versionType":"semver"},{"version":"6.15","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.18","versionEndExcluding":"6.1.138"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.18","versionEndExcluding":"6.6.90"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.18","versionEndExcluding":"6.12.28"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.18","versionEndExcluding":"6.14.6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.18","versionEndExcluding":"6.15"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/45aced97f01d5ab14c8a2a60f6748f18c501c3f5"},{"url":"https://git.kernel.org/stable/c/dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf"},{"url":"https://git.kernel.org/stable/c/f102342360950b56959e5fff4a874ea88ae13758"},{"url":"https://git.kernel.org/stable/c/d5c10448f411a925dd59005785cb971f0626e032"},{"url":"https://git.kernel.org/stable/c/38a05c0b87833f5b188ae43b428b1f792df2b384"}],"title":"irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs","x_generator":{"engine":"bippy-1.2.0"}},"adp":[{"title":"CVE Program Container","references":[{"url":"https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html"}],"providerMetadata":{"orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE","dateUpdated":"2025-11-03T19:57:06.588Z"}}]}}