cve/2024/CVE-2024-35793.md

### [CVE-2024-35793](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35793)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=6.7%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=8c88a474357ead632b07c70bf7f119ace8c3b39e%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)

### Description

In the Linux kernel, the following vulnerability has been resolved:debugfs: fix wait/cancellation handling during removeBen Greear further reports deadlocks during concurrent debugfsremove while files are being accessed, even though the code inquestion now uses debugfs cancellations. Turns out that despiteall the review on the locking, we missed completely that thelogic is wrong: if the refcount hits zero we can finish (andneed not wait for the completion), but if it doesn't we haveto trigger all the cancellations. As written, we can _never_get into the loop triggering the cancellations. Fix this, andexplain it better while at it.

### POC

#### Reference
- https://git.kernel.org/stable/c/e88b5ae01901c4a655a53158397746334778a57b

#### Github
No PoCs found on GitHub currently.