First published: Fri May 17 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: debugfs: fix wait/cancellation handling during remove Ben Greear further reports deadlocks during concurrent debugfs remove while files are being accessed, even though the code in question now uses debugfs cancellations. Turns out that despite all the review on the locking, we missed completely that the logic is wrong: if the refcount hits zero we can finish (and need not wait for the completion), but if it doesn't we have to trigger all the cancellations. As written, we can _never_ get into the loop triggering the cancellations. Fix this, and explain it better while at it.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.11-1 6.12.12-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-35793 has been categorized with a notable severity due to potential deadlocks during concurrent debugfs remove operations.
To mitigate CVE-2024-35793, ensure you update to the patched kernel versions, such as 5.10.223-1, 5.10.226-1, 6.1.123-1, or later.
CVE-2024-35793 affects various versions of the Linux kernel, specifically those prior to the fixed versions released by Debian.
The implications of CVE-2024-35793 include potential system stability issues due to deadlocks when accessing files during debugfs removals.
CVE-2024-35793 was reported by Ben Greear, highlighting issues with wait and cancellation handling in the debugfs system.