CVE-2026-64238
Received Received - Intake

Kernel Deadlock in GPIO Shared Proxy Removal

Publication date: 2026-07-24

Last updated on: 2026-07-24

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-24
Last Modified
2026-07-24
Generated
2026-07-24
AI Q&A
2026-07-24
EPSS Evaluated
N/A
NVD
CVE-2026-64238
EUVD
EUVD-2026-48647

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

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 in the Linux kernel involves a deadlock issue in the GPIO (General-Purpose Input/Output) subsystem. A fix was applied to a commit that used a mutex to protect a field called 'offset' in the GPIO shared proxy structure. The critical section was too large, causing a potential deadlock when removing the parent of a shared GPIO proxy.

Detection Guidance

This vulnerability is specific to the Linux kernel's GPIO subsystem and does not have network-based detection methods. It requires checking the kernel version and examining the GPIO shared proxy implementation for the described deadlock condition. Use commands like 'uname -a' to check kernel version and review kernel logs for GPIO-related errors or deadlocks.

Impact Analysis

This vulnerability could lead to system hangs or crashes when removing a parent device of a shared GPIO proxy. It may cause unexpected behavior in systems relying on GPIO functionality, potentially disrupting hardware interactions or device operations.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a Linux kernel GPIO subsystem issue involving a deadlock during shared proxy parent removal, which could lead to system instability but does not involve data privacy or security controls typically governed by these regulations.

Mitigation Strategies

Apply the kernel patch referenced in the CVE description (Commit 710abda58055) to fix the deadlock issue. Update your Linux kernel to a version that includes this fix. Monitor system logs for GPIO-related errors after applying the update.

Chat Assistant

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

EPSS Chart