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.

A flaw was found in the Linux kernel's `gpio: shared` component. A too wide critical section, intended to protect the `offset` field in the `struct gpio_shared_entry`, can lead to a potential deadlock. This occurs during the removal of a shared General Purpose Input/Output (GPIO) proxy's parent. A successful exploit of this vulnerability could result in a denial of service (DoS) due to system unresponsiveness.

Red Hat Enterprise Linux 10 Not affected kernel Red Hat Enterprise Linux 10 Fix deferred libkrun Red Hat Enterprise Linux 6 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel-rt Red Hat Enterprise Linux 8 Not affected kernel Red Hat Enterprise Linux 8 Not affected kernel-rt Red Hat Enterprise Linux 9 Not affected kernel Red Hat Enterprise Linux 9 Not affected kernel-rt Red Hat Enterprise Linux for NVIDIA 26 Out of support scope kernel Red Hat OpenShift Container Platform 4 Fix deferred rhcos https://www.cve.org/CVERecord?id=CVE-2026-64238 https://nvd.nist.gov/vuln/detail/CVE-2026-64238 https://lore.kernel.org/linux-cve-announce/2026072441-CVE-2026-64238-d9d5@gregkh/T