VulnerabilityPublished 15 Aug 2026Updated 6 Nov 2026

CVE-2026-72063: Linux kernel · gpio: tegra: do not call pinctrl for GPIO direction

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e57a4845b0da60a7b9f052160878097826320954 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in e57a4845b0da60a7b9f052160878097826320954, d3e91a95b2b0fc6336dbf3ec90d831a1654d2720, d3b92d16e1c4debec7526b6dbb2d98d0aeed796b +5

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 11da905412833d9b369a6a09a401f87149d674dc, < e57a4845b0da60a7b9f052160878097826320954	Fixed in e57a4845b0da60a7b9f052160878097826320954
LinuxLinux	Affected ≥ 11da905412833d9b369a6a09a401f87149d674dc, < d3e91a95b2b0fc6336dbf3ec90d831a1654d2720	Fixed in d3e91a95b2b0fc6336dbf3ec90d831a1654d2720
LinuxLinux	Affected ≥ 11da905412833d9b369a6a09a401f87149d674dc, < d3b92d16e1c4debec7526b6dbb2d98d0aeed796b	Fixed in d3b92d16e1c4debec7526b6dbb2d98d0aeed796b
LinuxLinux	Affected ≥ 11da905412833d9b369a6a09a401f87149d674dc, < cd17c5a1d9f186b57e9e2949be427803b7110a5c	Fixed in cd17c5a1d9f186b57e9e2949be427803b7110a5c
LinuxLinux	Affected ≥ 11da905412833d9b369a6a09a401f87149d674dc, < ac761e66708d51dac35c4c7f1891ea991dc788f0	Fixed in ac761e66708d51dac35c4c7f1891ea991dc788f0
LinuxLinux	Affected ≥ 11da905412833d9b369a6a09a401f87149d674dc, < 616188becd4a208afbae1653fc5241e1748bae80	Fixed in 616188becd4a208afbae1653fc5241e1748bae80

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.

References

Community reviews

Loading reviews…