CVE-2025-40303btrfs: ensure no dirty metadata is written back for an fs with errors
- 7.8HighCVSS base score
- 0.15%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 8 months later
· 8 months later
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 13e6c37b989859e70b0d73d3f2cb0aa022159b17 – < 066ee13f05fbd82ada01883e51f0695172f98dff
- affected 13e6c37b989859e70b0d73d3f2cb0aa022159b17 – < e2b3859067bf012d53c49b3f885fef40624a2c83
- affected 13e6c37b989859e70b0d73d3f2cb0aa022159b17 – < 54a5b5a15588e3b0b294df31474d08a2678d4291
- affected 13e6c37b989859e70b0d73d3f2cb0aa022159b17 – < 2618849f31e7cf51fadd4a5242458501a6d5b315
- affected 3.10
- unaffected < 3.10
- unaffected 6.6.117 – ≤ 6.6.*
- unaffected 6.12.58 – ≤ 6.12.*
- unaffected 6.17.8 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References4
- https://git.kernel.org/stable/c/066ee13f05fbd82ada01883e51f0695172f98dff (opens in a new tab)
- https://git.kernel.org/stable/c/e2b3859067bf012d53c49b3f885fef40624a2c83 (opens in a new tab)
- https://git.kernel.org/stable/c/54a5b5a15588e3b0b294df31474d08a2678d4291 (opens in a new tab)
- https://git.kernel.org/stable/c/2618849f31e7cf51fadd4a5242458501a6d5b315 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-201642 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-40303)Record last updated .