Linux Kernel up to 7.0.11 GPIO Shared gpio_chip::of_xlate offset deadlock

Summaryinfo

A vulnerability has been found in Linux Kernel up to 7.0.11 and classified as problematic. This affects the function gpio_chip::of_xlate of the component GPIO Shared. The manipulation of the argument offset leads to deadlock. This vulnerability is listed as CVE-2026-64238. The attack must be carried out locally. There is no available exploit.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.0.11 and classified as problematic. This issue affects the function gpio_chip::of_xlate of the component GPIO Shared. The manipulation of the argument offset with an unknown input leads to a deadlock vulnerability. Using CWE to declare the problem leads to CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. Impacted is availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-64238 since 07/19/2026. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but no exploit is available.

Upgrading to version 7.0.12 eliminates this vulnerability. Applying the patch a554dfcd30dd5e41d1d67387b3bb85cea83e12e1 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.0.8
• 7.0.9
• 7.0.10
• 7.0.11

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion