# CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes CVE-2026-53284 is fixed in 34 products on 1 platform, first by ALAS2023-2026-1866, released June 22, 2026. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2026-53284 - Priority: High - CVSS: 7.5 (Important) - EPSS: 0.0048 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Jun 22, 2026 - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-53284 ## Description In the Linux kernel, the following vulnerability has been resolved: btrfs: only release the dirty pages io tree after successful writes [WARNING] With extra warning on dirty extent buffers at umount (aka, the next patch in the series), test case generic/388 can trigger the following warning about dirty extent buffers at unmount time: BTRFS critical (device dm-2 state E): emergency shutdown BTRFS error (device dm-2 state E): error while writing out transaction: -30 BTRFS warning (device dm-2 state E): Skipping commit of aborted transaction. BTRFS error (device dm-2 state EA): Transaction 9 aborted (error -30) BTRFS: error (device dm-2 state EA) in cleanup_transaction:2068: errno=-30 Readonly filesystem BTRFS info (device dm-2 state EA): forced readonly BTRFS info (device dm-2 state EA): last unmount of filesystem 4fbf2e15-f941-49a0-bc7c-716315d2777c ------------[ cut here ]------------ WARNING: disk-io.c:3311 at invalidate_and_check_btree_folios+0xfd/0x1ca [btrfs], CPU#8: umount/914368 CPU: 8 UID: 0 PID: 914368 Comm: umount Tainted: G OE 7.1.0-rc1-custom+ #372 PREEMPT(full) 2de38db8d1deae71fde295430a0ff3ab98ccf596 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022 RIP: 0010:invalidate_and_check_btree_folios+0xfd/0x1ca [btrfs] Call Trace: close_ctree+0x52e/0x574 [btrfs d2f0b1cd330d1287e7a9919d112eadfc0e914efd] generic_shutdown_super+0x89/0x1a0 kill_anon_super+0x16/0x40 btrfs_kill_super+0x16/0x20 [btrfs d2f0b1cd330d1287e7a9919d112eadfc0e914efd] deactivate_locked_super+0x2d/0xb0 cleanup_mnt+0xdc/0x140 task_work_run+0x5a/0xa0 exit_to_user_mode_loop+0x123/0x4b0 do_syscall_64+0x243/0x7c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 ---[ end trace 0000000000000000 ]--- BTRFS warning (device dm-2 state EA): unable to release extent buffer 30539776 owner 9 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30621696 owner 257 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30638080 owner 258 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30654464 owner 7 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30703616 owner 2 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30720000 owner 10 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30736384 owner 4 gen 9 refs 2 flags 0x7 BTRFS warning (device dm-2 state EA): unable to release extent buffer 30752768 owner 11 gen 9 refs 2 flags 0x7 I'm using a stripped down version, which seems to trigger the warning more reliably: _fsstress_pid="" workload() { dmesg -C mkfs.btrfs -f -K $dev > /dev/null echo 1 > /sys/kernel/debug/clear_warn_once mount $dev $mnt $fsstress -w -n 1024 -p 4 -d $mnt & _fsstress_pid=$! sleep 0 $godown $mnt pkill --echo -PIPE fsstress > /dev/null wait $_fsstress_pid unset _fsstress_pid umount $mnt if dmesg | grep -q "WARNING"; then fail fi } for (( i = 0; i < $runtime; i++ )); do echo "=== $i/$runtime ===" workload done [CAUSE] Inside btrfs_write_and_wait_transaction(), we first try to write all dirty ebs, then wait for them to finish. After that we call btrfs_extent_io_tree_release() to free all extent states from dirty_pages io tree. However if we hit an error from btrfs_write_marked_extent(), then we still call btrfs_extent_io_tree_release() to clear that dirty_pages io tree, which may contain dirty records that we haven't yet submitted. Furthermore, the later transaction cleanup path will utilize that dirty_pages io tree to properly cleanup those dirty ebs, but since it's already empty, no dirty ebs are properly cleaned up, thus will later trigger the warnings inside invalidate_btree_folios(). ---truncated--- ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-64kb sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-64kb sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-azure opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-azure sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-azure sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-default sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.38.1.160000.2.22 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-default-base sles 15.7 | 6.4.0-150700.53.84.1.150700.17.47.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-default-base sles 16.0 | 6.12.0-160000.38.1.160000.2.23 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-docs sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-docs sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-livepatch-6.18.33-63.124 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel-livepatch-SLE15-SP7-RT_Update_21 sles 15.7 | 1-150700.1.3.1 | [SUSE-SU-2026:4640-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4640-1.md) | Nov 7, 2026 | | Linux | kernel-livepatch-SLE15-SP7_Update_22 sles 15.7 | 1-150700.15.3.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-obs-build sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-source sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-source sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-syms sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-syms sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.38.1 | [OPENSUSE-SU-2026:21910-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-21910-1.md) | Sep 22, 2026 | | Linux | kernel-zfcpdump sles 15.7 | 6.4.0-150700.53.84.1 | [SUSE-SU-2026:4706-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-4706-1.md) | Nov 7, 2026 | | Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.38.1 | [SUSE-SU-2026:23902-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-23902-1.md) | Sep 22, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | linux Debian 13.5 (trixie) | 6.12.115-2 | [DEBIAN-CVE-2026-53284](https://patchblox.com/security/data/fix/linux/debian-cve-2026-53284.md) | Jun 27, 2026 | | Linux | linux Debian 14 | 7.0.10-1 | [DEBIAN-CVE-2026-53284](https://patchblox.com/security/data/fix/linux/debian-cve-2026-53284.md) | Jun 27, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.33-63.124.amzn2023 | [ALAS2023-2026-1866](https://patchblox.com/security/data/fix/linux/alas2023-2026-1866.md) | Jun 22, 2026 | --- Data as of 2026-11-08T13:06:02Z 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.