CVE-2025-40303

published 8 Dec 2025 · updated 5 Aug 2026

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

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 066ee13f05fbd82ada01883e51f0695172f98dff, Kernel 2618849f31e7cf51fadd4a5242458501a6d5b315, Kernel 54a5b5a15588e3b0b294df31474d08a2678d4291 and 1 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=3.10, >=13e6c37b989859e70b0d73d3f2cb0aa022159b17 <066ee13f05fbd82ada01883e51f0695172f98dff, >=13e6c37b989859e70b0d73d3f2cb0aa022159b17 <2618849f31e7cf51fadd4a5242458501a6d5b315, >=13e6c37b989859e70b0d73d3f2cb0aa022159b17 <54a5b5a15588e3b0b294df31474d08a2678d4291, >=13e6c37b989859e70b0d73d3f2cb0aa022159b17 <e2b3859067bf012d53c49b3f885fef40624a2c83066ee13f05fbd82ada01883e51f0695172f98dff, 2618849f31e7cf51fadd4a5242458501a6d5b315, 54a5b5a15588e3b0b294df31474d08a2678d4291, e2b3859067bf012d53c49b3f885fef40624a2c83

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-40303 severity on Zeptric[![CVE-2025-40303](https://zeptric.io/badge/cve/CVE-2025-40303.svg)](https://zeptric.io/cve/CVE-2025-40303)