VDB

CVE-2026-72063

CVE-2026-72063 PUBLISHED

gpio: tegra: do not call pinctrl for GPIO direction

Reported by linux · Published August 15, 2026

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.12Amazon Linux1:6.12.100-125.179.amzn2023
kernel6.12-develAmazon Linux1:6.12.100-125.179.amzn2023
python3-perf6.12Amazon Linux1:6.12.100-125.179.amzn2023
kernel6.18-develAmazon Linux1:6.18.41-94.142.amzn2023
LinuxLinuxe57a4845b0da60a7b9f052160878097826320954, d3e91a95b2b0fc6336dbf3ec90d831a1654d2720, d3b92d16e1c4debec7526b6dbb2d98d0aeed796b, cd17c5a1d9f186b57e9e2949be427803b7110a5c, ac761e66708d51dac35c4c7f1891ea991dc788f0, 89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49, 628c63f96f4564fa145f602af2d41daf9532201f, 616188becd4a208afbae1653fc5241e1748bae80, 5.1

Affected products

VendorProductVersions
LinuxLinux11da905412833d9b369a6a09a401f87149d674dc, 11da905412833d9b369a6a09a401f87149d674dc, 11da905412833d9b369a6a09a401f87149d674dc
LinuxLinux5.1, 0, 5.10.266
amazon:2023kernel6.120
amazon:2023kernel6.12-devel0
amazon:2023python3-perf6.120
amazon:2023kernel6.18-devel0
LinuxLinux6.12.97, 6.6.148, 6.1.184
amazon:2023microvm-kernel6.180
amazon:2023kernel6.18-tools0
amazon:2023kernel6.12-modules-extra0
amazon:2023python3-perf6.180
amazon:2023kernel6.180
amazon:2023kernel6.18-headers0
amazon:2023perf6.180
amazon:2023bpftool6.180
amazon:2023kernel6.12-tools0
linuxlinux_kernel5.1, 5.1, 5.1
amazon:2023kernel6.12-headers0
amazon:2023bpftool6.120
amazon:2023kernel-livepatch-6.12.100-125.1790

…and 7 more

Timeline

  • Aug 15, 2026 Coalition ESS Score
  • Aug 15, 2026 CVE Published
  • Aug 19, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (17 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-72063
vulnetix vdb fixes CVE-2026-72063

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72063/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›