# CVE-2025-40303: btrfs: ensure no dirty metadata is written back for an fs with errors CVE-2025-40303 is fixed in 36 products on 1 platform, first by DEBIAN-CVE-2025-40303, released December 8, 2025. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2025-40303 - Priority: High - CVSS: 7.8 (Moderate) - EPSS: 0.0015 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Dec 8, 2025 - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-40303 ## 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. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.12 amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | bpftool6.12-debuginfo amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-64kb sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-azure opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-azure sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-default sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.9.1.160000.2.6 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-default-base sles 16.0 | 6.12.0-160000.9.1.160000.2.6 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-docs sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-livepatch-6.12.58-82.121 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-source sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-syms sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.9.1 | [OPENSUSE-SU-2026:20145-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-20145-1.md) | Feb 2, 2026 | | Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.9.1 | [SUSE-SU-2026:20220-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20220-1.md) | Feb 2, 2026 | | Linux | kernel6.12 amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-debuginfo amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-debuginfo-common-aarch64 amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-debuginfo-common-x86_64 amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-devel amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-headers amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-libbpf amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-libbpf-debuginfo amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-libbpf-devel amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-libbpf-static amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-modules-extra amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-modules-extra-common amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-tools amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-tools-debuginfo amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | kernel6.12-tools-devel amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | linux Debian 13.5 (trixie) | 6.12.63-1 | [DEBIAN-CVE-2025-40303](https://patchblox.com/security/data/fix/linux/debian-cve-2025-40303.md) | Dec 8, 2025 | | Linux | linux Debian 14 | 6.17.8-1 | [DEBIAN-CVE-2025-40303](https://patchblox.com/security/data/fix/linux/debian-cve-2025-40303.md) | Dec 8, 2025 | | Linux | perf6.12 amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | perf6.12-debuginfo amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | python3-perf6.12 amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | | Linux | python3-perf6.12-debuginfo amzn 2023 | 1:6.12.58-82.121.amzn2023 | [ALAS2023-2026-1495](https://patchblox.com/security/data/fix/linux/alas2023-2026-1495.md) | Mar 16, 2026 | --- Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.