gpio: shared: fix deadlock on shared proxy's parent removal
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a554dfcd30dd5e41d1d67387b3bb85cea83e12e1, Kernel 7.0.12, Kernel a1b836607304f71051f9f9dcccf8b5097b86a1fb and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=710abda58055ed5eaa8958107633cc12a365c328 <a554dfcd30dd5e41d1d67387b3bb85cea83e12e1, >=7.0.1 <7.0.12, =7.0, =7.1, >=710abda58055ed5eaa8958107633cc12a365c328 <a1b836607304f71051f9f9dcccf8b5097b86a1fb, >=6.19.12 <7.0, =28f488e7b327630686378bb1d24e22cfc3fc162d, >=6.19.12 <6.20 | a554dfcd30dd5e41d1d67387b3bb85cea83e12e1, 7.0.12, a1b836607304f71051f9f9dcccf8b5097b86a1fb, 7.0, 6.20 |
| linux-kernel: Kernel | >=6.19.12 <6.20, >=7.0.0 <7.0.12 | 6.20, 7.0.12 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket