Menu

Star on GitHub · 3.2k

CVE-2025-40101

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(…

Published Oct 30, 2025EPSS 0.20%

Overview

CVE-2025-40101 is a known-severity vulnerability. It was published on October 30, 2025.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-40101?

CVE-2025-40101 is a known-severity vulnerability. It was published on October 30, 2025.

How severe is CVE-2025-40101?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-40101?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-40101?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-40101 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.