The Linux kernel Tegra GPIO driver makes an unnecessary call to the pinctrl framework when setting a GPIO’s direction. Because the pinctrl mutex can sleep, this call is executed while the driver holds an atomic‑context spinlock, violating kernel locking rules. The resulting sleep‑in‑atomic warning can cause a deadlock, kernel panic, or system hang, potentially leading to denial of service for the entire machine. The vulnerability is an instance of improper locking (CWE‑663). Based on the description, it is inferred that an attacker who can trigger the affected driver path might bring the system down, but the CVE does not disclose a direct exploitation vector or privilege escalation mechanism.

Any Linux kernel that includes the tegra_gpio driver, which is built for Tegra SoCs, may be impacted. The CVE data lists no specific kernel version, so all kernels shipping the affected driver could be affected.

The CVSS score of 5.5 indicates medium severity. The EPSS score of less than 1% suggests a low likelihood of exploitation, and the vulnerability is not listed in CISA KEV. The attack vector lies in internal kernel code; an attacker would need to exercise the path that calls tegra_gpio_direction_input/output while holding a GPIO spinlock. While the risk to confidentiality or integrity is low, a successful trigger could result in a kernel panic or lockup, causing a high impact on availability.