VDB

CVE-2025-40303

CVE-2025-40303 PUBLISHED CVSS 7.8 HIGH

btrfs: ensure no dirty metadata is written back for an fs with errors

Reported by linux · Published December 8, 2025

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 transaction is allowed thus metadata is in a frozen state. But there are some metadata modifications before that error, and they are still in the btree inode page cache. Since there will be no real transaction commit, all those dirty folios are just kept as is in the page cache, and they can not be invalidated by invalidate_inode_pages2() call inside close_ctree(), because they are dirty. And finally after btrfs_stop_all_workers(), we call iput() on btree inode, which triggers writeback of those dirty metadata. And if the fs is using RAID56 metadata, this will trigger RMW and queue new works into rmw_workers, which is already stopped, causing warning from queue_work() and use-after-free. [FIX] Add a special handling for write_one_eb(), that if the fs is already in an error state, immediately mark the bbio as failure, instead of really submitting them. Then during close_ctree(), iput() will just discard all those dirty tree blocks without really writing them back, thus no more new jobs for already stopped-and-freed workqueues. The extra discard in write_one_eb() also acts as an extra safenet. E.g. the transaction abort is triggered by some extent/free space tree corruptions, and since extent/free space tree is already corrupted some tree blocks may be allocated where they shouldn't be (overwriting existing tree blocks). In that case writing them back will further corrupting the fs.

EPSS 0.15% · 4.0th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.12-libbpf-develAmazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-tools-develAmazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-toolsAmazon Linux1:6.12.58-82.121.amzn2023
bpftool6.12Amazon Linux1:6.12.58-82.121.amzn2023
perf6.12Amazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-develAmazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-headersAmazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-libbpf-staticAmazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-libbpfAmazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-modules-extra-commonAmazon Linux1:6.12.58-82.121.amzn2023
kernel6.12-modules-extraAmazon Linux1:6.12.58-82.121.amzn2023
LinuxLinux3.10, 2618849f31e7cf51fadd4a5242458501a6d5b315, 066ee13f05fbd82ada01883e51f0695172f98dff

Risk scores

CVSS 3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score
0.15%
4.0th percentile

Affected products

VendorProductVersions
LinuxLinux13e6c37b989859e70b0d73d3f2cb0aa022159b17, 13e6c37b989859e70b0d73d3f2cb0aa022159b17, 13e6c37b989859e70b0d73d3f2cb0aa022159b17
LinuxLinux3.10, 0, 6.6.117
amazon:2023kernel6.12-libbpf-devel0
amazon:2023kernel6.12-tools-devel0
amazon:2023kernel6.12-tools0
amazon:2023bpftool6.120
amazon:2023perf6.120
amazon:2023kernel6.12-devel0
amazon:2023kernel6.12-headers0
amazon:2023kernel6.12-libbpf-static0
amazon:2023kernel6.12-libbpf0
amazon:2023kernel6.12-modules-extra-common0
amazon:2023kernel6.12-modules-extra0
amazon:2023python3-perf6.120
amazon:2023kernel6.120
LinuxLinux6.18, 6.12.58, 6.17.8
amazon:2023kernel-livepatch-6.12.58-82.1210
linuxlinux_kernel3.10, 3.10, 3.10

Timeline

  • Oct 11, 2025 PoC Published (38 in total, the first dated here)
  • Dec 7, 2025 CVE Published
  • Dec 8, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (166 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (204 in total, the first dated here)
  • Jun 8, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-40303
vulnetix vdb fixes CVE-2025-40303

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-40303/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›