- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (11 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 11da905412833d9b369a6a09a401f87149d674dc – < 89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49
- affected 11da905412833d9b369a6a09a401f87149d674dc – < d3b92d16e1c4debec7526b6dbb2d98d0aeed796b
- affected 11da905412833d9b369a6a09a401f87149d674dc – < 616188becd4a208afbae1653fc5241e1748bae80
- affected 11da905412833d9b369a6a09a401f87149d674dc – < e57a4845b0da60a7b9f052160878097826320954
- affected 11da905412833d9b369a6a09a401f87149d674dc – < cd17c5a1d9f186b57e9e2949be427803b7110a5c
- affected 11da905412833d9b369a6a09a401f87149d674dc – < ac761e66708d51dac35c4c7f1891ea991dc788f0
- affected 11da905412833d9b369a6a09a401f87149d674dc – < 628c63f96f4564fa145f602af2d41daf9532201f
- affected 11da905412833d9b369a6a09a401f87149d674dc – < d3e91a95b2b0fc6336dbf3ec90d831a1654d2720
- affected 5.1
- unaffected < 5.1
- unaffected 5.10.266 – ≤ 5.10.*
- unaffected 5.15.217 – ≤ 5.15.*
- unaffected 6.1.184 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49 (opens in a new tab)
- https://git.kernel.org/stable/c/d3b92d16e1c4debec7526b6dbb2d98d0aeed796b (opens in a new tab)
- https://git.kernel.org/stable/c/616188becd4a208afbae1653fc5241e1748bae80 (opens in a new tab)
- https://git.kernel.org/stable/c/e57a4845b0da60a7b9f052160878097826320954 (opens in a new tab)
- https://git.kernel.org/stable/c/cd17c5a1d9f186b57e9e2949be427803b7110a5c (opens in a new tab)
- https://git.kernel.org/stable/c/ac761e66708d51dac35c4c7f1891ea991dc788f0 (opens in a new tab)
- https://git.kernel.org/stable/c/628c63f96f4564fa145f602af2d41daf9532201f (opens in a new tab)
- https://git.kernel.org/stable/c/d3e91a95b2b0fc6336dbf3ec90d831a1654d2720 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59021 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72063)Record last updated .