CVE-2026-64238
Last modified
CVE-2026-64238 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 710abda58055ed5eaa8958107633cc12a365c328, < a554dfcd30dd5e41d1d67387b3bb85cea83e12e1; >= 710abda58055ed5eaa8958107633cc12a365c328, < a1b836607304f71051f9f9dcccf8b5097b86a1fb; 28f488e7b327630686378bb1d24e22cfc3fc162d; >= 6.19.12, < 6.20 |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64238?
How severe is CVE-2026-64238?
How do I fix CVE-2026-64238?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64232In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64233In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64234In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64235In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64236In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64237In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64239In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6424Use-after-free vulnerability in ESET Linux products potentia…6.7
- CVE-2026-64240In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64241In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64242In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64243In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-64238?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
