LiveActive security incident?Get immediate response
CVE Record

CVE-2025-40101: btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST At the end of btrfs_load_block_group_zone_info() the first thing we do is to ensure that if the mapping type is not a SINGLE one and there is no RAID stripe tree, then we return early with an error. Doing that, though, prevents the code from running the last calls from this function which are about freeing memory allocated during its run. Hence, in this case, instead of returning early, we set the ret value and fall through the rest of the cleanup code.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a Btrfs memory leak on an error path. When certain unsupported Btrfs profile conditions are rejected, cleanup was skipped. The public data does not show code execution, privilege escalation, or confirmed exploitation.

Executive priority

Treat as routine kernel maintenance unless your environment heavily uses Btrfs. There is no provided evidence of active exploitation or severe impact, but kernel memory leaks can affect reliability.

Technical view

In btrfs_load_block_group_zone_info(), a non-SINGLE mapping without a RAID stripe tree returned early with an error before freeing allocated memory. The fix changes control flow to set ret and fall through cleanup.

Likely exposure

Exposure appears limited to Linux systems using Btrfs where this specific non-SINGLE data profile without RAID stripe tree condition can occur. The provided version metadata is incomplete and should be verified against kernel.org stable branch status.

Exploitation context

The bundle does not cite active exploitation, KEV listing, exploit availability, or a practical attack path. The described impact is memory leakage during rejection of an invalid Btrfs configuration path.

Researcher notes

The core issue is an early return bypassing cleanup in btrfs_load_block_group_zone_info(). Analysis should focus on whether reachable configurations can repeatedly trigger allocations without cleanup and whether vendor kernels backported the fix.

Mitigation direction

  • Check kernel.org stable commits and vendor advisories for your running kernel branch.
  • Update to a kernel build containing the referenced Btrfs cleanup fix.
  • Prioritize systems using Btrfs, especially with zoned storage or RAID-related profiles.
  • If patching is delayed, monitor Btrfs error logs and memory pressure.

Validation and detection

  • Inventory Linux hosts and identify kernels running Btrfs filesystems.
  • Compare running kernel versions with vendor fixed builds and kernel.org stable commits.
  • Review Btrfs mount and storage profiles for non-SINGLE or RAID-related configurations.
  • Check vendor advisories because the supplied affected-version data is ambiguous.
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-2025-40101 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5906333cc4af7b3fdb8cfff1cb3e8e579bd13174, 5906333cc4af7b3fdb8cfff1cb3e8e579bd13174, 5906333cc4af7b3fdb8cfff1cb3e8e579bd13174, 6ffeca99bf6e84800133d21afd41c79d2f002db7, 6.7.11unaffected
LinuxLinux6.8, 0, 6.12.55, 6.17.5, 6.18affected
Weakness

CWE details

No CWE listed

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