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.
History

Tue, 22 Oct 2024 02:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-833

Thu, 12 Sep 2024 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 11 Sep 2024 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2024-05-17T12:24:56.630Z

Updated: 2024-11-05T09:22:28.117Z

Reserved: 2024-05-17T12:19:12.339Z

Link: CVE-2024-35793

cve-icon Vulnrichment

Updated: 2024-08-02T03:21:47.366Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-05-17T13:15:59.023

Modified: 2024-05-17T18:35:35.070

Link: CVE-2024-35793

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-05-17T00:00:00Z

Links: CVE-2024-35793 - Bugzilla