# CVE-2026-72063: gpio: tegra: do not call pinctrl for GPIO direction

Status: published. Published: 2026-08-15. Updated: 2026-11-06.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 11da905412833d9b369a6a09a401f87149d674dc; < 89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49 (affected, git); ≥ 11da905412833d9b369a6a09a401f87149d674dc; < d3b92d16e1c4debec7526b6dbb2d98d0aeed796b (affected, git); ≥ 11da905412833d9b369a6a09a401f87149d674dc; < 616188becd4a208afbae1653fc5241e1748bae80 (affected, git); ≥ 11da905412833d9b369a6a09a401f87149d674dc; < e57a4845b0da60a7b9f052160878097826320954 (affected, git); ≥ 11da905412833d9b369a6a09a401f87149d674dc; < cd17c5a1d9f186b57e9e2949be427803b7110a5c (affected, git); ≥ 11da905412833d9b369a6a09a401f87149d674dc; < ac761e66708d51dac35c4c7f1891ea991dc788f0 (affected, git); ≥ 11da905412833d9b369a6a09a401f87149d674dc; < 628c63f96f4564fa145f602af2d41daf9532201f (affected, git); ≥ 11da905412833d9b369a6a09a401f87149d674dc; < d3e91a95b2b0fc6336dbf3ec90d831a1654d2720 (affected, git). Source: CNA: Linux
- Linux / Linux: 5.1 (affected); ≥ 0; < 5.1 (unaffected, semver); ≥ 5.10.266; ≤ 5.10.* (unaffected, semver); ≥ 5.15.217; ≤ 5.15.* (unaffected, semver); ≥ 6.1.184; ≤ 6.1.* (unaffected, semver); ≥ 6.6.148; ≤ 6.6.* (unaffected, semver); ≥ 6.12.97; ≤ 6.12.* (unaffected, semver); ≥ 6.18.40; ≤ 6.18.* (unaffected, semver); ≥ 7.1.5; ≤ 7.1.* (unaffected, semver); ≥ 7.2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.22% as of 2026-11-06; percentile 12.61%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49 (CNA: Linux)

- https://git.kernel.org/stable/c/d3b92d16e1c4debec7526b6dbb2d98d0aeed796b (CNA: Linux)

- https://git.kernel.org/stable/c/616188becd4a208afbae1653fc5241e1748bae80 (CNA: Linux)

- https://git.kernel.org/stable/c/e57a4845b0da60a7b9f052160878097826320954 (CNA: Linux)

- https://git.kernel.org/stable/c/cd17c5a1d9f186b57e9e2949be427803b7110a5c (CNA: Linux)

- https://git.kernel.org/stable/c/ac761e66708d51dac35c4c7f1891ea991dc788f0 (CNA: Linux)

- https://git.kernel.org/stable/c/628c63f96f4564fa145f602af2d41daf9532201f (CNA: Linux)

- https://git.kernel.org/stable/c/d3e91a95b2b0fc6336dbf3ec90d831a1654d2720 (CNA: Linux)

- https://git.kernel.org/stable/c/616188becd4a208afbae1653fc5241e1748bae80 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/628c63f96f4564fa145f602af2d41daf9532201f (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/89904b4f1dc0f9550c3f206dcdfceed0b7ce7c49 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/ac761e66708d51dac35c4c7f1891ea991dc788f0 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/cd17c5a1d9f186b57e9e2949be427803b7110a5c (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/d3b92d16e1c4debec7526b6dbb2d98d0aeed796b (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/d3e91a95b2b0fc6336dbf3ec90d831a1654d2720 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/e57a4845b0da60a7b9f052160878097826320954 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-72063; retrieved 2026-11-06; source updated 2026-11-06

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72063; retrieved 2026-11-06; source updated 2026-11-06

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-72063; retrieved 2026-11-06; source updated Not reported

Revision: 3ee146206495df12e91f3210489e5d2144abbb25e5bc1a56dd90260390acd7f2

Canonical: https://y2.dev/cve/CVE-2026-72063

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.