CVE-2024-35935: btrfs: send: handle path ref underflow in header iterate_inode_ref()
In the Linux kernel, the following vulnerability has been resolved:
btrfs: send: handle path ref underflow in header iterate_inode_ref()
Change BUG_ON to proper error handling if building the path buffer
fails. The pointers are not printed so we don't accidentally leak kernel
addresses.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Btrfs issue in the send path. The public description says a failure while building a path buffer could hit a kernel BUG condition instead of returning an error. Business urgency depends on whether affected Linux kernels and Btrfs send are used.
Executive priority
Schedule this into normal kernel patching unless Btrfs is business-critical or exposed in managed appliance environments. Escalate priority for systems where kernel crashes would affect production availability.
Technical view
The flaw is in Btrfs send, specifically iterate_inode_ref(). The fix replaces BUG_ON behavior with normal error handling when path buffer construction fails, and avoids printing pointers to prevent accidental kernel address leakage. The bundle does not provide CVSS, CWE, or detailed attacker prerequisites.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with Btrfs functionality, especially where Btrfs send is used. Distribution package status must be checked because the bundle lists upstream stable commits and Debian LTS advisories, not every vendor kernel.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. No exploit details, public proof-of-concept status, or attacker access requirements are provided. Treat this as a kernel reliability and hardening issue until vendor guidance gives clearer impact.
Researcher notes
Evidence is limited to the CVE description, upstream stable references, and Debian LTS advisories. The source bundle names no CVSS score, CWE, exploit activity, or precise attacker model. Avoid assuming remote exploitability or privilege escalation without vendor evidence.
Mitigation direction
Apply vendor kernel updates that include the referenced stable Btrfs fixes.
Check Debian LTS advisories if using Debian-based long-term support systems.
Prioritize hosts using Btrfs send or Btrfs-backed operational workflows.
If no package fix is available, follow your Linux vendor's mitigation guidance.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and images.
Identify systems using Btrfs filesystems or Btrfs send workflows.
Compare installed kernels against vendor advisories and fixed package versions.
Confirm patched kernels are booted, not only installed.
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-35935 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.