CVE-2026-72063gpio: tegra: do not call pinctrl for GPIO direction
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 23, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 11da905412833d9b369a6a09a401f87149d674dc before 89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49; from 11da905412833d9b369a6a09a401f87149d674dc before d3b92d16e1c4debec7526b6dbb2d98d0aeed796b; from 11da905412833d9b369a6a09a401f87149d674dc before 616188becd4a208afbae1653fc5241e1748bae80; from 11da905412833d9b369a6a09a401f87149d674dc before e57a4845b0da60a7b9f052160878097826320954; from 11da905412833d9b369a6a09a401f87149d674dc before cd17c5a1d9f186b57e9e2949be427803b7110a5c; from 11da905412833d9b369a6a09a401f87149d674dc before ac761e66708d51dac35c4c7f1891ea991dc788f0; from 11da905412833d9b369a6a09a401f87149d674dc before 628c63f96f4564fa145f602af2d41daf9532201f; from 11da905412833d9b369a6a09a401f87149d674dc before d3e91a95b2b0fc6336dbf3ec90d831a1654d2720 | CNA record |
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
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.