LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35793: debugfs: fix wait/cancellation handling during remove

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw can deadlock the system when debugfs entries are removed while their files are being accessed. This can disrupt availability. The supplied CVSS assessment also rates confidentiality and integrity impacts as high, although the description specifically documents deadlocks rather than explaining those impacts.

Executive priority

Prioritize internet-facing, multi-user, and sensitive Linux systems where local accounts or workloads may reach debugfs. Treat remediation as high priority, but avoid assuming remote compromise: the supplied vector is local and requires privileges. Coordinate normal kernel patching and reboot procedures promptly.

Technical view

The debugfs removal path handled its reference count incorrectly. When references remained, it should initiate cancellations before waiting, but the faulty condition made that cancellation loop unreachable. Concurrent removal and file access could therefore deadlock. The referenced stable-kernel commits correct this wait and cancellation logic.

Likely exposure

The supplied record marks Linux kernel releases 6.7, 6.7.12, 6.8.3, and 6.9 as affected. Exposure depends on the deployed kernel, vendor backports, and whether local users can reach relevant debugfs operations. Distribution package versions cannot be inferred from upstream numbering alone.

Exploitation context

The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The bundle provides no evidence of active exploitation, and the record is not flagged as CISA KEV. The documented failure scenario requires concurrent debugfs removal and file access.

Researcher notes

No CWE is supplied. The description establishes a deadlock caused by unreachable cancellation logic, but does not substantiate how confidentiality or integrity loss would occur despite the CVSS values. Exact vulnerable ranges and downstream backport status should be confirmed through vendor advisories and commit ancestry.

Mitigation direction

  • Install the vendor-supported kernel update containing the referenced debugfs correction.
  • Check distribution advisories for backported fixes before relying on upstream version numbers.
  • Restrict unnecessary local access to affected systems while patching is pending.
  • Review vendor guidance if an updated kernel is not yet available.

Validation and detection

  • Record each system's running kernel and distribution package version.
  • Confirm the installed package includes one of the referenced stable fixes or an equivalent backport.
  • Reboot after updating and verify the corrected kernel is running.
  • Run authorized regression tests covering concurrent debugfs access and removal.
  • Monitor kernel logs and system hangs for recurring debugfs-related symptoms.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-35793 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-35793Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8c88a474357ead632b07c70bf7f119ace8c3b39e, 8c88a474357ead632b07c70bf7f119ace8c3b39e, 8c88a474357ead632b07c70bf7f119ace8c3b39eunaffected
LinuxLinux6.7, 0, 6.7.12, 6.8.3, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.