CVE-2026-64238: gpio: shared: fix deadlock on shared proxy's parent removal
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 gpiochip::ofxlate() if set") used the mutex embedded in struct gpiosharedentry 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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64238?
CVE-2026-64238 has a medium severity rating of 5.5 according to CVSS 3.1.
How do I fix CVE-2026-64238?
To fix CVE-2026-64238, apply the available patch provided by the Linux kernel.
What is the risk associated with CVE-2026-64238?
CVE-2026-64238 poses a risk level of 32, indicating potential vulnerabilities in shared proxies within the Linux kernel.
What systems are affected by CVE-2026-64238?
CVE-2026-64238 affects the Linux kernel and systems running affected versions.
What is the impact of CVE-2026-64238?
The impact of CVE-2026-64238 involves potential deadlocks during the removal of a shared proxy's parent.