VulnerabilityPublished 30 Oct 2025

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

Source GCVE Database

Compare

Not known to be exploited.

Data as of 29 Oct 2026, 23:09 UTC

Severity

Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-qqwh-7pmj-9xx8

What to do

AI-suggested

A fix has been implemented in the Linux kernel to address this memory leak by ensuring proper cleanup of allocated memory in the affected function. Users should update to the fixed kernel version once it is available. No additional mitigation steps are indicated.

Description

A memory leak vulnerability in the Linux kernel's btrfs filesystem code was fixed. The issue occurred when rejecting a non SINGLE data profile without a RAID stripe tree, causing early return that skipped memory cleanup. The fix ensures proper cleanup by setting an error return value and continuing with memory freeing operations.

Impact

The vulnerability causes memory leaks in the kernel when handling certain btrfs data profiles, which could lead to increased memory usage and potential system instability over time. There is no indication of direct exploitation or further impact such as privilege escalation or data corruption.

Summary

CVE-2025-40101 addresses a memory leak in the Linux kernel's btrfs filesystem. Specifically, in the function btrfs_load_block_group_zone_info(), if the mapping type is not SINGLE and there is no RAID stripe tree, the function previously returned early with an error, bypassing the cleanup code that frees allocated memory. The patch modifies this behavior to set the error return value but still execute the cleanup code, preventing memory leaks.

References

Community reviews

Loading reviews…