Vulnerability 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 Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.19.12, < 7.0 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/a1b836607304f71051f9f9dcccf8b5097b86a1fbPatch
- https://git.kernel.org/stable/c/a554dfcd30dd5e41d1d67387b3bb85cea83e12e1Patch
FAQ
What is CVE-2026-64238?
CVE-2026-64238 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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"...
How severe is CVE-2026-64238?
CVE-2026-64238 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-64238?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.