CVE-2026-97501pinctrl: mediatek: paris: bypass pinctrl GPIO layer in set GPIO direction
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 36 days later
· 36 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 – < f1536772cb3e4aa8d63988051f6fd6e4bb005cf7
- affected 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 – < 482ba972f9638f467df2d498b46384a1d1f80529
- affected 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 – < 3c4897861759fd8bd81dc2ada92121ac76332592
- affected 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 – < 428b031dad390edd5da729b9afd474a95dc4f76b
- affected 805250982bb5c5ce4a6e52e1d87204c5feea0dd1 – < c87c9046c4e00d599454e033a477176c4d73ac2a
- affected 4.20
- unaffected < 4.20
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/f1536772cb3e4aa8d63988051f6fd6e4bb005cf7 (opens in a new tab)
- https://git.kernel.org/stable/c/482ba972f9638f467df2d498b46384a1d1f80529 (opens in a new tab)
- https://git.kernel.org/stable/c/3c4897861759fd8bd81dc2ada92121ac76332592 (opens in a new tab)
- https://git.kernel.org/stable/c/428b031dad390edd5da729b9afd474a95dc4f76b (opens in a new tab)
- https://git.kernel.org/stable/c/c87c9046c4e00d599454e033a477176c4d73ac2a (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86099 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97501)Record last updated .