CVEvulnerability
CVE-2024-35793
5.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2024-05-17
- Last modified
- 2026-08-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-667
Description
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.
Affected configurations
• linux linux kernel (>= 6.7.1 < 6.7.12)
• linux linux kernel (>= 6.8 < 6.8.3)
• linux linux kernel 6.7
Related
Weakness · CWE (1)
- CWE-667 Improper Locking weakness
References
- https://git.kernel.org/stable/c/3d08cca5fd0aabb62b7015067ab40913b33da906 Patch
- https://git.kernel.org/stable/c/952c3fce297f12c7ff59380adb66b564e2bc9b64 Patch
- https://git.kernel.org/stable/c/e88b5ae01901c4a655a53158397746334778a57b Patch
- https://git.kernel.org/stable/c/3d08cca5fd0aabb62b7015067ab40913b33da906 Patch
- https://git.kernel.org/stable/c/952c3fce297f12c7ff59380adb66b564e2bc9b64 Patch
- https://git.kernel.org/stable/c/e88b5ae01901c4a655a53158397746334778a57b Patch