SECUFOCUSNOW
Home›CVE index›CVE-2025-40303
Review reviewHigh

CVE-2025-40303

Linux

In the Linux kernel, the following vulnerability has been resolved: btrfs: ensure no dirty metadata is written back for an fs with errors [BUG] During development of a minor feature (make sure all btrfs_bio::end_io() is called in task context), I noticed a crash in generic/388, where metadata writes triggered new works after btrfs_stop_all_workers(). It turns out that it can even happen without any code modification, just using RAID5 for metadata and the same workload from generic/388 is going to trigger the use-after-free. [CAUSE] If btrfs hits an error, the fs is marked as error, no new t...

CVSS
7.8
EPSS
0.14%
3.51% percentile
CISA KEV
Not listed
Published
2025.12.08
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: btrfs: ensure no dirty metadata is written back for an fs with errors [BUG] During development of a minor feature (make sure all btrfs_bio::end_io() is called in task context), I noticed a crash in generic/388, where metadata writes triggered new works after btrfs_stop_all_workers(). It turns out that it can even happen without any code modification, just using RAID5 for metadata and the same workload from generic/388 is going to trigger the use-after-free. [CAUSE] If btrfs hits an error, the fs is marked as error, no new t...

Affected product and versions

Product
Linux
Affected versions
>= 13e6c37b989859e70b0d73d3f2cb0aa022159b17 < 066ee13f05fbd82ada01883e51f0695172f98dff, >= 13e6c37b989859e70b0d73d3f2cb0aa022159b17 < e2b3859067bf012d53c49b3f885fef40624a2c83, >= 13e6c37b989859e70b0d73d3f2cb0aa022159b17 < 54a5b5a15588e3b0b294df31474d08a2678d4291, >= 13e6c37b989859e70b0d73d3f2cb0aa022159b17 < 2618849f31e7cf51fadd4a5242458501a6d5b315, >= 3.10
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available