CVE-2024-46841: btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc()
In the Linux kernel, the following vulnerability has been resolved:
btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc()
We handle errors here properly, ENOMEM isn't fatal, return the error.
Security readout for executives and security teams
Plain-English summary
This Linux kernel Btrfs issue can turn a recoverable out-of-memory condition into a kernel BUG, potentially crashing the system. The business concern is service availability for systems using Btrfs, especially under memory pressure. The sources do not provide CVSS scoring or evidence of active exploitation.
Executive priority
Treat this as a targeted kernel availability risk, not a confirmed active exploitation emergency. Prioritize patching production Linux systems using Btrfs and rely on vendor kernel updates rather than custom workarounds.
Technical view
In Btrfs, walk_down_proc() incorrectly used BUG_ON when btrfs_lookup_extent_info() returned ENOMEM. The fix changes handling so ENOMEM is returned as a normal error. This is a kernel availability flaw tied to Btrfs code paths; exact exposure depends on kernel branch and distribution backports.
Likely exposure
Exposure is most likely on Linux systems using Btrfs with affected kernel versions or unpatched vendor kernels. Systems not using Btrfs are less likely to be practically exposed, but kernel package status should still be checked against vendor guidance.
Exploitation context
The source bundle does not indicate public exploitation, exploit code, or inclusion in CISA KEV. The plausible impact is denial of service through a kernel BUG under an ENOMEM condition, but the sources do not document real-world attack conditions.
Researcher notes
Evidence is limited to the CVE text, Linux stable commit references, and Debian LTS announcements. No CVSS, CWE, exploit status, or detailed affected range is provided in the bundle. Avoid assuming remote reachability or privilege requirements without vendor detail.
Mitigation direction
Update to a vendor kernel containing the referenced stable Btrfs fixes.
Follow Linux distribution advisories for backported kernel packages.
Apply Debian LTS kernel updates where Debian LTS systems are in scope.
Reboot systems after kernel updates so the fixed kernel is active.
Prioritize Btrfs hosts supporting production or availability-sensitive workloads.
Validation and detection
Inventory Linux hosts and identify those using Btrfs filesystems.
Record running kernel versions, not only installed package versions.
Compare kernel packages with vendor advisories and stable fix references.
For Debian LTS, check the cited March 2025 advisory coverage.
Confirm hosts booted into the patched kernel after maintenance.
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-46841 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.