pinctrl: qcom: msm: mark certain pins as invalid for interrupts
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f365be0925729508fd8e62f8bdb504ef896cb6e0 · < 275605a8b48002fe98675a5c06f3e39c09067ff2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
pinctrl: qcom: msm: mark certain pins as invalid for interrupts
On some platforms, the UFS-reset pin has no interrupt logic in TLMM but is nevertheless registered as a GPIO in the kernel. This enables the user-space to trigger a BUG() in the pinctrl-msm driver by running, for example: `gpiomon -c 0 113` on RB2.
The exact culprit is requesting pins whose intr_detection_width setting is not 1 or 2 for interrupts. This hits a BUG() in msm_gpio_irq_set_type(). Potentially crashing the kernel due to an invalid request from user-space is not optimal, so let's go through the pins and mark those that would fail the check as invalid for the irq chip as we should not even register them as available irqs.
This function can be extended if we determine that there are more corner-cases like this.
From the CVE record · Linux
On some platforms, pins without interrupt logic are registered as GPIOs in the Linux kernel. A local user-space request for an interrupt on one of these pins can trigger a BUG() in the pinctrl-msm driver and potentially crash the kernel. The input does not specify authentication requirements.
Engineers running Linux kernels on platforms with affected Qualcomm MSM GPIO pins should check their systems; affected versions are not specified.