Security readout for executives and security teams
Plain-English summary
A race in Linux Btrfs error handling can account the same write twice, release related state too early, and crash the kernel. The demonstrated case uses 4K Btrfs sectors on a 64K-page AArch64 system. This is primarily a host stability and availability concern; the supplied CVSS also rates potential confidentiality and integrity impact highly.
Executive priority
Prioritize patching exposed multi-user, shared-hosting, and availability-critical Btrfs systems. Accelerate systems matching the demonstrated 64K-page and 4K-sector configuration. For other environments, inventory first and schedule remediation through normal high-severity kernel maintenance. No supplied evidence supports declaring an active exploitation emergency.
Technical view
When btrfs_run_delalloc_range() fails, overlapping page writeback and error cleanup can finish the same ordered extent twice. That double accounting can cause premature release, use-after-free behavior, a NULL-pointer dereference, and kernel panic. The supplied record assigns CVSS 3.1 score 7.8 with local access, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is greatest on affected Linux systems actively using Btrfs, particularly AArch64 hosts combining 64K memory pages with 4K filesystem sectors. A local low-privileged user may be positioned to trigger the vulnerable write path. The supplied version data is unusual and insufficient for confidently defining every vulnerable distribution build; confirm status with kernel vendors.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public weaponized exploit. It documents reproducible kernel crashes during filesystem testing. The demonstrated outcome is denial of service; broader confidentiality and integrity consequences are represented by the CVSS assessment but are not demonstrated in the supplied narrative.
Researcher notes
The failure sequence involves overlapping extent_writepage processing and delalloc cleanup after an error, causing duplicate ordered-extent completion. The record associates CWE-770, although the narrative describes accounting corruption and premature lifetime termination. Researchers should distinguish the demonstrated panic from the broader CVSS impacts. Exact vulnerable and fixed distribution versions require vendor mapping to the cited commits.
Mitigation direction
- Install a vendor-supported kernel containing the applicable upstream stable fix.
- Confirm the chosen distribution build maps to one of the cited Linux stable commits.
- Where feasible, avoid experimental 4K-sector Btrfs configurations on 64K-page systems until updated.
- Maintain tested backups and recovery procedures for affected Btrfs hosts.
- Review Linux and distribution vendor guidance for any additional mitigations or corrected version ranges.
Validation and detection
- Inventory Linux hosts using Btrfs and record kernel, architecture, page size, and filesystem sector size.
- Prioritize AArch64 systems with 64K pages and Btrfs filesystems using 4K sectors.
- Check kernel logs for delalloc failures, bad ordered extent accounting, NULL dereferences, or panics.
- Verify installed kernel provenance includes the applicable cited stable fix.
- After updating, run approved Btrfs regression and recovery testing in a non-production environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-58089 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/21333148b5c9e52f41fafcedec3810b56a5e0e40CVE reference, Linux
- https://git.kernel.org/stable/c/0283ee1912c8e243c931f4ee5b3672e954fe0384CVE reference, Linux
- https://git.kernel.org/stable/c/72dad8e377afa50435940adfb697e070d3556670CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.