debugfs: fix wait/cancellation handling during remove (Linux Linux)

CVE-2024-35793
HIGH 7.8

At a glance

Source
NVD
EPSS
EPSS 0.18 % · percentile 8 ()
State
PUBLISHED
Published
Updated
Assigner
Linux
NVD status
Modified

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.

Weaknesses (CWE)

References

Scores

VersionScoreVectorScored by
CVSS 3.1HIGH 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux
CVSS 3.1HIGH 7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HNVD · 416baaa9-dc9f-4396-8d5f-8c081fb06d67 (Secondary)
CVSS 3.1MEDIUM 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HNVD · nvd@nist.gov (Primary)

European references

CERT-FR advisories

Affected configurations (NVD CPE)

Affected products

ProductVersions
Linux · Linuxaffected 8c88a474357ead632b07c70bf7f119ace8c3b39e < e88b5ae01901c4a655a53158397746334778a57b ; affected 8c88a474357ead632b07c70bf7f119ace8c3b39e < 3d08cca5fd0aabb62b7015067ab40913b33da906 ; affected 8c88a474357ead632b07c70bf7f119ace8c3b39e < 952c3fce297f12c7ff59380adb66b564e2bc9b64
Linux · Linuxaffected 6.7 ; unaffected 0 < 6.7 ; unaffected 6.7.12 ≤ 6.7.* ; unaffected 6.8.3 ≤ 6.8.* ; unaffected 6.9 ≤ *

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD