CVE-2026-72063
Received Received - Intake

Tegra GPIO Direction Handling Race Condition

Vulnerability report for CVE-2026-72063, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-23

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-23
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nvidia tegra *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves the Linux kernel's GPIO handling for Tegra devices. The issue is that the tegra_gpio_direction_input() and tegra_gpio_direction_output() functions unnecessarily call pinctrl functions to set GPIO direction. These extra calls enter the pinctrl core and take a mutex, which can cause a sleep-in-atomic-context issue when GPIO users hold a spinlock.

Detection Guidance

This vulnerability is specific to the Linux kernel's Tegra GPIO driver and does not have a direct network detection method. Detection involves checking the kernel version and verifying if the vulnerable code path exists in the tegra_gpio_direction_input() or tegra_gpio_direction_output() functions. Use commands like 'uname -a' to check the kernel version and 'dmesg | grep tegra' to inspect GPIO-related logs for errors.

Impact Analysis

This vulnerability can cause system instability or crashes due to sleep-in-atomic-context errors. Systems using shared GPIO lines with Tegra devices may experience kernel warnings or failures when GPIO direction changes occur while holding spinlocks.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA as it is a low-level Linux kernel issue related to GPIO handling in the Tegra platform. It may indirectly impact systems relying on GPIO operations in regulated environments if it causes instability or unexpected behavior.

Mitigation Strategies

Apply the latest kernel update from your Linux distribution to ensure the vulnerable code is patched. If an update is not immediately available, consider recompiling the kernel with the redundant pinctrl direction calls removed from tegra_gpio_direction_input() and tegra_gpio_direction_output(). Monitor system logs for GPIO-related errors after applying changes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72063. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart