CVE-2026-97501

pinctrl: mediatek: paris: bypass pinctrl GPIO layer in set GPIO direction

Description

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.

Key facts

Published
24 Sep 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.165% likely to be exploited in the next 30 days, higher than 5.726% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 up to but excluding f1536772cb3e4aa8d63988051f6fd6e4bb005cf7 (affected)
  • 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 up to but excluding 482ba972f9638f467df2d498b46384a1d1f80529 (affected)
  • 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 up to but excluding 3c4897861759fd8bd81dc2ada92121ac76332592 (affected)
  • 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 up to but excluding 428b031dad390edd5da729b9afd474a95dc4f76b (affected)
  • 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 up to but excluding c87c9046c4e00d599454e033a477176c4d73ac2a (affected)
LinuxLinux
  • Default status: affected
  • 4.20 (affected)
  • 0 up to but excluding 4.20 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References