CVE-2025-37901 (GCVE-0-2025-37901)

Vulnerability from cvelistv5 – Published: 2025-05-20 15:21 – Updated: 2026-08-05 11:58
VLAI
Title
irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs
Summary
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.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: a6199bb514d8a63f61c2a22c1f912376e14d0fb2 , < 45aced97f01d5ab14c8a2a60f6748f18c501c3f5 (git)
Affected: a6199bb514d8a63f61c2a22c1f912376e14d0fb2 , < dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf (git)
Affected: a6199bb514d8a63f61c2a22c1f912376e14d0fb2 , < f102342360950b56959e5fff4a874ea88ae13758 (git)
Affected: a6199bb514d8a63f61c2a22c1f912376e14d0fb2 , < d5c10448f411a925dd59005785cb971f0626e032 (git)
Affected: a6199bb514d8a63f61c2a22c1f912376e14d0fb2 , < 38a05c0b87833f5b188ae43b428b1f792df2b384 (git)
Create a notification for this product.
Linux Linux Affected: 5.18
Unaffected: 0 , < 5.18 (semver)
Unaffected: 6.1.138 , ≤ 6.1.* (semver)
Unaffected: 6.6.90 , ≤ 6.6.* (semver)
Unaffected: 6.12.28 , ≤ 6.12.* (semver)
Unaffected: 6.14.6 , ≤ 6.14.* (semver)
Unaffected: 6.15 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T19:57:06.588Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/irqchip/irq-qcom-mpm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "45aced97f01d5ab14c8a2a60f6748f18c501c3f5",
              "status": "affected",
              "version": "a6199bb514d8a63f61c2a22c1f912376e14d0fb2",
              "versionType": "git"
            },
            {
              "lessThan": "dfbaecf7e38f5e9bfa5e47a1e525ffbb58bab8cf",
              "status": "affected",
              "version": "a6199bb514d8a63f61c2a22c1f912376e14d0fb2",
              "versionType": "git"
            },
            {
              "lessThan": "f102342360950b56959e5fff4a874ea88ae13758",
              "status": "affected",
              "version": "a6199bb514d8a63f61c2a22c1f912376e14d0fb2",
              "versionType": "git"
            },
            {
              "lessThan": "d5c10448f411a925dd59005785cb971f0626e032",
              "status": "affected",
              "version": "a6199bb514d8a63f61c2a22c1f912376e14d0fb2",
              "versionType": "git"
            },
            {
              "lessThan": "38a05c0b87833f5b188ae43b428b1f792df2b384",
              "status": "affected",
              "version": "a6199bb514d8a63f61c2a22c1f912376e14d0fb2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/irqchip/irq-qcom-mpm.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.18"
            },
            {
              "lessThan": "5.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.138",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.90",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.28",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.14.*",
              "status": "unaffected",
              "version": "6.14.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.138",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.90",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.28",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14.6",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15",
                  "versionStartIncluding": "5.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "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\u0027s 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": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerability is reached through the GPIO character device ioctl path (`gpio_ioctl` \u2192 `linereq_create` \u2192 `edge_detector_setup` \u2192 `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 \u2014 a single `gpiomon -c gpiochipN \u003cline\u003e` on any GPIO absent from the SoC\u0027s `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\u0027s 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, \u0026val, ...)` 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\u0027d 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(\u0026priv-\u003elock)` with interrupts disabled \u2014 so `priv-\u003elock` is orphaned and all later MPM operations, including the wake handler and the suspend path, deadlock."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:58:11.172Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "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"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-37901",
    "datePublished": "2025-05-20T15:21:36.062Z",
    "dateReserved": "2025-04-16T04:51:23.965Z",
    "dateUpdated": "2026-08-05T11:58:11.172Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-37901",
      "date": "2026-11-19",
      "epss": "0.00214",
      "percentile": "0.11838"
    },
    "microsoft_vex": {
      "current_release_date": "2026-02-18T14:29:39.000Z",
      "cve": "CVE-2025-37901",
      "id": "msrc_CVE-2025-37901",
      "initial_release_date": "2025-07-11T00:00:00.000Z",
      "product_status:fixed": "2",
      "product_status:known_affected": "2",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs",
      "url": "https://msrc.microsoft.com/csaf/vex/2025/msrc_cve-2025-37901.json",
      "version": "2"
    },
    "redhat_vex": {
      "aggregate_severity": "Low",
      "current_release_date": "2026-11-09T18:26:35+00:00",
      "cve": "CVE-2025-37901",
      "id": "CVE-2025-37901",
      "initial_release_date": "2025-05-20T00:00:00+00:00",
      "product_status:known_not_affected": "200",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-37901.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.