CVE-2025-71268: btrfs: fix reservation leak in some error paths when inserting inline extent
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix reservation leak in some error paths when inserting inline extent
If we fail to allocate a path or join a transaction, we return from
__cow_file_range_inline() without freeing the reserved qgroup data,
resulting in a leak. Fix this by ensuring we call btrfs_qgroup_free_data()
in such cases.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel btrfs accounting leak. Under certain error conditions, storage quota reservation data is not released. The public record does not quantify impact, but kernel resource leaks can affect reliability. Prioritize systems using btrfs and plan normal kernel patching unless vendor guidance raises urgency.
Executive priority
Treat this as a near-term kernel maintenance item for Linux assets using btrfs. Escalate priority if btrfs supports critical services, shared hosting, or vendor advisories later assign higher severity or exploitation evidence.
Technical view
In btrfs __cow_file_range_inline(), failures allocating a path or joining a transaction could return without btrfs_qgroup_free_data(), leaking reserved qgroup data. Stable commits add cleanup in those error paths. The public record does not state privilege requirements, reachable configurations, CVSS, or CWE.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds and using btrfs. The qgroup cleanup detail suggests quota-group accounting is involved, but the provided sources do not define required mount options, distro status, or affected deployment patterns.
Exploitation context
No active exploitation is supported by the supplied sources, and KEV is false. The record describes a kernel error-path resource leak, not a public exploit chain. Attacker prerequisites and practical trigger conditions are not provided.
Researcher notes
Triage should focus on btrfs inline extent insertion error paths and qgroup reservation cleanup. Confirm whether downstream kernels include one of the stable fixes or an equivalent backport. The bundle lacks reproducer details, exploitability analysis, CVSS, CWE, and distro-specific status.
Mitigation direction
Apply kernel updates containing the referenced stable btrfs fixes.
Check Linux distribution advisories for equivalent backported fixes.
Prioritize btrfs hosts supporting critical storage or multi-tenant workloads.
Monitor vendor guidance for severity, impact, and configuration-specific mitigations.
Validation and detection
Inventory Linux hosts using btrfs filesystems.
Compare running kernel builds against vendor-fixed packages or referenced stable commits.
Check whether btrfs quota-group features are enabled where relevant.
Review kernel and storage monitoring for resource pressure on btrfs hosts.
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-2025-71268 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.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
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.
Mar 18, 2026, 17:40 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.