pinctrl: mediatek: paris: bypass pinctrl GPIO layer in set GPIO direction
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Partial Red Hat: 1 without a fix
No CVSS vector from any source. Fix status from CNA and Red Hat.
Summary
In the Linux kernel, the following vulnerability has been resolved: pinctrl: mediatek: paris: bypass pinctrl GPIO layer in set GPIO direction pinctrl_gpio_direction_input() / pinctrl_gpio_direction_output() take the pinctrl mutex. This causes a gpiochip operations to need to sleep. Worse yet, the .can_sleep field in the gpiochip is not set. This causes the shared GPIO proxy to trip over, as it uses gpiod_cansleep() to check whether it can use a spinlock or needs a mutex. In this case, it ends up taking a spinlock, then calls pinctrl_gpio_direction_output(), which takes a mutex. This causes a huge warning. While this class of Mediatek hardware does not have separate clear/set registers, the pinctrl context has a spinlock that is taken whenever a register read-modify-write is done. Also, once the GPIO function is selected / muxed in, further GPIO operations do not involve pinctrl operations or state. The GPIO direction and level values do not require toggling the pinmux or any other pin config options. Switch to directly calling mtk_pinmux_gpio_set_direction() in the GPIO set direction callbacks to avoid taking the pinctrl mutex. Drop the .gpio_set_direction field in mtk_pmxops to signal we are no longer using the pinctrl GPIO layer for setting the direction.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
- Fix · CNA Linux (Linux) Fixed in 6.1.191, 6.6.160, 6.12.114, 6.18.53, 7.2
Vendor assessments
Red Hat
Red Hat rating: Low. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Enterprise Linux 10 | Affected | No fix yet: Fix deferred |
Not affected: 6 products
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 7
- Red Hat Enterprise Linux 8
- Red Hat Enterprise Linux 9
- Red Hat OpenShift Container Platform 4
- Red Hat OpenShift Container Platform 5
Timeline
- 2026-10-02 Threatist record created from CVE-2026-97501
- 2026-10-03 Alias added: GHSA-gwq5-76j7-fm2x
- 2026-10-21 Fix available: Linux/Linux@3c4897861759fd8bd81dc2ada92121ac76332592, Linux/Linux@482ba972f9638f467df2d498b46384a1d1f80529, Linux/[email protected] +1 · CNA
- 2026-10-21 2 new references · CNA
- 2026-10-30 Fix available: Linux/[email protected], Linux/Linux@f1536772cb3e4aa8d63988051f6fd6e4bb005cf7 · CNA
- 2026-10-30 1 new reference · CNA
- 2026-11-07 Affected versions changed · Red Hat
References
Other 5
- https://git.kernel.org/stable/c/f1536772cb3e4aa8d63988051f6fd6e4bb005cf7
- https://git.kernel.org/stable/c/482ba972f9638f467df2d498b46384a1d1f80529
- https://git.kernel.org/stable/c/3c4897861759fd8bd81dc2ada92121ac76332592
- https://git.kernel.org/stable/c/428b031dad390edd5da729b9afd474a95dc4f76b
- https://git.kernel.org/stable/c/c87c9046c4e00d599454e033a477176c4d73ac2a
More Linux vulnerabilities
- TI-2025-26358 tls: fix handling of zero-length records on the rx_list KEVCVSS 3.1CRITICAL 9.8
- TI-2026-38352 netfilter: bridge: make ebt_snat ARP rewrite writable KEVCVSS 3.1HIGH 8.8
- TI-2021-02452 Incorrect authorization in Ubuntu linux kernel KEVCVSS 3.1HIGH 8.8
- TI-2013-05264 The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the… KEVCVSS 3.1HIGH 8.8
- TI-2022-00125 Integer overflow in kernel KEVCVSS 3.1HIGH 8.4
- TI-2013-01864 The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9… KEVCVSS 3.1HIGH 8.4
Sources
- CVE-2026-97501 · CVE Program
- CVE-2026-97501 · NVD
- FIRST EPSS
- GHSA-gwq5-76j7-fm2x · GitHub Advisory Database · CC BY 4.0
- CVE-2026-97501 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences