Vulnerability · Published Jun 3, 2026 · Assigned by Linux

CVE-2026-46251btrfs: fix block_group_tree dirty_list corruption

High 8.4

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.4High
Exploit odds (30 days)0.1%top 97.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix block_group_tree dirty_list corruption When the incompat flag EXTENT_TREE_V2 is set, we unconditionally add the block group tree to the switch_commits list before calling switch_commit_roots, as we do for the tree root and the chunk root. However, the block group tree uses normal root dirty tracking and in any transaction that does an allocation and dirties a block group, the block group root will already be linked to a list by the dirty_list field and this use of list_add_tail() is invalid and corrupts the prev/next members of block_group_root->dirty_list. This is apparent on a subsequent list_del on the prev if we enable CONFIG_DEBUG_LIST: [32.1571] ------------[ cut here ]------------ [32.1572] list_del corruption. next->prev should beffff958890202538, but was ffff9588992bd538. (next=ffff958890201538) [32.1575] WARNING: lib/list_debug.c:65 at 0x0, CPU#3: sync/607 [32.1583] CPU: 3 UID: 0 PID: 607 Comm: sync Not tainted 6.18.0 #24PREEMPT(none) [32.1585] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS1.17.0-4.fc41 04/01/2014 [32.1587] RIP: 0010:__list_del_entry_valid_or_report+0x108/0x120 [32.1593] RSP: 0018:ffffaa288287fdd0 EFLAGS: 00010202 [32.1594] RAX: 0000000000000001 RBX: ffff95889326e800 RCX:ffff958890201538 [32.1596] RDX: ffff9588992bd538 RSI: ffff958890202538 RDI:ffffffff82a41e00 [32.1597] RBP: ffff958890202538 R08: ffffffff828fc1e8 R09:00000000ffffefff [32.1599] R10: ffffffff8288c200 R11: ffffffff828e4200 R12:ffff958890201538 [32.1601] R13: ffff95889326e958 R14: ffff958895c24000 R15:ffff958890202538 [32.1603] FS: 00007f0c28eb5740(0000) GS:ffff958af2bd2000(0000)knlGS:0000000000000000 [32.1605] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [32.1607] CR2: 00007f0c28e8a3cc CR3: 0000000109942005 CR4:0000000000370ef0 [32.1609] Call Trace: [32.1610] <TASK> [32.1611] switch_commit_roots+0x82/0x1d0 [btrfs] [32.1615] btrfs_commit_transaction+0x968/0x1550 [btrfs] [32.1618] ? btrfs_attach_transaction_barrier+0x23/0x60 [btrfs] [32.1621] __iterate_supers+0xe8/0x190 [32.1622] ? __pfx_sync_fs_one_sb+0x10/0x10 [32.1623] ksys_sync+0x63/0xb0 [32.1624] __do_sys_sync+0xe/0x20 [32.1625] do_syscall_64+0x73/0x450 [32.1626] entry_SYSCALL_64_after_hwframe+0x76/0x7e [32.1627] RIP: 0033:0x7f0c28d05d2b [32.1632] RSP: 002b:00007ffc9d988048 EFLAGS: 00000246 ORIG_RAX:00000000000000a2 [32.1634] RAX: ffffffffffffffda RBX: 00007ffc9d988228 RCX:00007f0c28d05d2b [32.1636] RDX: 00007f0c28e02301 RSI: 00007ffc9d989b21 RDI:00007f0c28dba90d [32.1637] RBP: 0000000000000001 R08: 0000000000000001 R09:0000000000000000 [32.1639] R10: 0000000000000000 R11: 0000000000000246 R12:000055b96572cb80 [32.1641] R13: 000055b96572b19f R14: 00007f0c28dfa434 R15:000055b96572b034 [32.1643] </TASK> [32.1644] irq event stamp: 0 [32.1644] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [32.1646] hardirqs last disabled at (0): [<ffffffff81298817>]copy_process+0xb37/0x2260 [32.1648] softirqs last enabled at (0): [<ffffffff81298817>]copy_process+0xb37/0x2260 [32.1650] softirqs last disabled at (0): [<0000000000000000>] 0x0 [32.1652] ---[ end trace 0000000000000000 ]--- Furthermore, this list corruption eventually (when we happen to add a new block group) results in getting the switch_commits and dirty_cowonly_roots lists mixed up and attempting to call update_root on the tree root which can't be found in the tree root, resulting in a transaction abort: [87.8269] BTRFS critical (device nvme1n1): unable to find root key (1 0 0) in tree 1 [87.8272] ------------[ cut here ]------------ [87.8274] BTRFS: Transaction aborted (error -117) [87.8275] WARNING: fs/btrfs/root-tree.c:153 at 0x0, CPU#4: sync/703 [87.8285] CPU: 4 UID: 0 PID: 703 Comm: sync Not tainted 6.18.0 #25 PREEMPT(none) [87.8287] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-4.fc41 0 ---truncated---

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.170-1DEBIAN-CVE-2026-46251
Debian:13linux6.12.85-1DEBIAN-CVE-2026-46251
Debian:14linux6.18.14-1DEBIAN-CVE-2026-46251
Ubuntu:24.04:LTSlinux6.8.0-134.134UBUNTU-CVE-2026-46251
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-aws6.8.0-1060.63UBUNTU-CVE-2026-46251
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1060.63~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure6.8.0-1063.71UBUNTU-CVE-2026-46251
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1063.71~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure-fde6.8.0-1062.69UBUNTU-CVE-2026-46251
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-azure-fde-6.86.8.0-1062.69~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-gcp6.8.0-1063.69UBUNTU-CVE-2026-46251
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1063.69~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-gke6.8.0-1058.64UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1045.48UBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-136.136~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-ibm6.8.0-1060.61UBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1060.61~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-134.134.1UBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-134.134.1~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1058.61UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1058.61~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1058.61.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1029.30UBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-oracle6.8.0-1057.58UBUNTU-CVE-2026-46251
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1057.58~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-raspi6.8.0-1060.64UBUNTU-CVE-2026-46251
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46251
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46251
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-134.134~22.04.1UBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-46251
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-46251
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1032.33UBUNTU-CVE-2026-46251

Affected products (as reported)

VendorProductVersions
Linux Linux 14033b08a02916e85ffc5397e4ac15337359f3ae – before 6e10283b5519d987d880d71bec90cdc7f2ec62b314033b08a02916e85ffc5397e4ac15337359f3ae – before e3d1fd084319f8f0830b22f014c7af6a96b4497b14033b08a02916e85ffc5397e4ac15337359f3ae – before 4eb830847d84276f1c8ea46541cfeeedaba1fb6314033b08a02916e85ffc5397e4ac15337359f3ae – before 80e1fda9c084dcf54819a12bc7682ec0afd2d8f414033b08a02916e85ffc5397e4ac15337359f3ae – before 201091da34c4f113af6b4a7407091c39bf29d4ca14033b08a02916e85ffc5397e4ac15337359f3ae – before 3a1f4264daed4b419c325a7fe35e756cada3cf82dabf41db56f378a360ff0219c467f8dfecda7dd66.0.19 – before 6.1
Linux Linux 6.1

References