Answer in brief
CVE-2024-35793 records a Unknown severity vulnerability in debugfs: fix wait/cancellation handling during remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8c88a474357ead632b07c70bf7f119ace8c3b39e <e88b5ae01901c4a655a53158397746334778a57b || >=8c88a474357ead632b07c70bf7f119ace8c3b39e <3d08cca5fd0aabb62b7015067ab40913b33da906 || >=8c88a474357ead632b07c70bf7f119ace8c3b39e <952c3fce297f12c7ff59380adb66b564e2bc9b64 | e88b5ae01901c4a655a53158397746334778a57b, 3d08cca5fd0aabb62b7015067ab40913b33da906, 952c3fce297f12c7ff59380adb66b564e2bc9b64 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-35793 records a Unknown severity vulnerability in debugfs: fix wait/cancellation handling during remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8c88a474357ead632b07c70bf7f119ace8c3b39e <e88b5ae01901c4a655a53158397746334778a57b || >=8c88a474357ead632b07c70bf7f119ace8c3b39e <3d08cca5fd0aabb62b7015067ab40913b33da906 || >=8c88a474357ead632b07c70bf7f119ace8c3b39e <952c3fce297f12c7ff59380adb66b564e2bc9b64 | e88b5ae01901c4a655a53158397746334778a57b, 3d08cca5fd0aabb62b7015067ab40913b33da906, 952c3fce297f12c7ff59380adb66b564e2bc9b64 |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.