CVE-2026-46251

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. the CNA's CVSS baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

A fix is available — apply it.

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] [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] [32.1644] irq event stamp: 0 [32.1644] hardirqs last enabled at (0): [<0000000000000000>] 0x0 [32.1646] hardirqs last disabled at (0): []copy_process+0xb37/0x2260 [32.1648] softirqs last enabled at (0): []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---

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 3, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jun 5, 2026
No patch confirmed yet.
generic

btrfs: fix block_group_tree dirty_list corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e3d1fd084319f8f0830b22f014c7af6a96b4497b
generic

btrfs: fix block_group_tree dirty_list corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80e1fda9c084dcf54819a12bc7682ec0afd2d8f4
generic

btrfs: fix block_group_tree dirty_list corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e10283b5519d987d880d71bec90cdc7f2ec62b3
generic

btrfs: fix block_group_tree dirty_list corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4eb830847d84276f1c8ea46541cfeeedaba1fb63
generic

btrfs: fix block_group_tree dirty_list corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a1f4264daed4b419c325a7fe35e756cada3cf82
generic

btrfs: fix block_group_tree dirty_list corruption - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/201091da34c4f113af6b4a7407091c39bf29d4ca

Vendor Advisories for CVE-2026-46251(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1055.56~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1057.58~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
linuxKernel @ 6.1.165—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1—

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 275 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 05:33 UTCEG score recompute
  3. 2026-09-14 05:33 UTCVendor advisory
  4. 2026-09-14 05:33 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 23:36 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 03:38 UTCEG score recompute
  23. 2026-08-25 03:38 UTCVendor advisory
  24. 2026-08-25 03:38 UTCGHSA enrichment
  25. 2026-08-24 00:43 UTCVendor advisory
Show 75 more
  1. 2026-08-24 00:42 UTCGHSA enrichment
  2. 2026-08-23 12:49 UTCEG score recompute
  3. 2026-08-23 12:49 UTCVendor advisory
  4. 2026-08-23 12:49 UTCGHSA enrichment
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 14:41 UTCEG score recompute
  8. 2026-08-21 14:41 UTCVendor advisory
  9. 2026-08-21 14:41 UTCGHSA enrichment
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 21:48 UTCVendor advisory
  12. 2026-08-20 21:47 UTCGHSA enrichment
  13. 2026-08-20 10:02 UTCEG score recompute
  14. 2026-08-20 10:02 UTCVendor advisory
  15. 2026-08-20 10:01 UTCGHSA enrichment
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-17 15:48 UTCEG score recompute
  18. 2026-08-17 15:48 UTCVendor advisory
  19. 2026-08-17 15:48 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 03:45 UTCVendor advisory
  22. 2026-08-17 03:45 UTCGHSA enrichment
  23. 2026-08-16 14:57 UTCEG score recompute
  24. 2026-08-16 14:57 UTCVendor advisory
  25. 2026-08-16 14:57 UTCGHSA enrichment
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 02:29 UTCEG score recompute
  28. 2026-08-16 02:29 UTCVendor advisory
  29. 2026-08-16 02:29 UTCGHSA enrichment
  30. 2026-08-16 02:14 UTCEPSS rescore
  31. 2026-08-15 14:44 UTCEG score recompute
  32. 2026-08-15 14:44 UTCVendor advisory
  33. 2026-08-15 14:44 UTCGHSA enrichment
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-14 22:43 UTCVendor advisory
  36. 2026-08-14 22:43 UTCGHSA enrichment
  37. 2026-08-14 10:58 UTCVendor advisory
  38. 2026-08-14 10:58 UTCGHSA enrichment
  39. 2026-08-13 23:13 UTCEG score recompute
  40. 2026-08-13 23:13 UTCVendor advisory
  41. 2026-08-13 23:13 UTCGHSA enrichment
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-13 10:06 UTCVendor advisory
  44. 2026-08-13 10:06 UTCGHSA enrichment
  45. 2026-08-12 22:20 UTCEG score recompute
  46. 2026-08-12 22:20 UTCVendor advisory
  47. 2026-08-12 22:20 UTCGHSA enrichment
  48. 2026-08-12 13:51 UTCEPSS rescore
  49. 2026-08-12 10:36 UTCVendor advisory
  50. 2026-08-12 10:35 UTCGHSA enrichment
  51. 2026-08-11 22:32 UTCEG score recompute
  52. 2026-08-11 22:32 UTCVendor advisory
  53. 2026-08-11 22:32 UTCGHSA enrichment
  54. 2026-08-11 10:48 UTCEG score recompute
  55. 2026-08-11 10:48 UTCVendor advisory
  56. 2026-08-11 10:48 UTCGHSA enrichment
  57. 2026-08-11 00:00 UTCEPSS rescore
  58. 2026-08-10 23:02 UTCVendor advisory
  59. 2026-08-10 23:02 UTCGHSA enrichment
  60. 2026-08-10 11:17 UTCVendor advisory
  61. 2026-08-10 11:17 UTCGHSA enrichment
  62. 2026-08-09 23:31 UTCEG score recompute
  63. 2026-08-09 23:31 UTCVendor advisory
  64. 2026-08-09 23:31 UTCGHSA enrichment
  65. 2026-08-09 13:46 UTCEPSS rescore
  66. 2026-08-09 11:46 UTCVendor advisory
  67. 2026-08-09 11:46 UTCGHSA enrichment
  68. 2026-08-08 23:56 UTCEG score recompute
  69. 2026-08-08 23:56 UTCVendor advisory
  70. 2026-08-08 23:56 UTCGHSA enrichment
  71. 2026-08-08 16:37 UTCEPSS rescore
  72. 2026-08-08 12:11 UTCVendor advisory
  73. 2026-08-08 12:11 UTCGHSA enrichment
  74. 2026-08-08 00:25 UTCEG score recompute
  75. 2026-08-08 00:25 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46251?
CVE-2026-46251 is a high vulnerability published on June 3, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: fix blockgrouptree dirty_list corruption When the incompat flag EXTENTTREEV2 is set, we unconditionally add the block group tree to the switch_commits list before calling switchcommitroots, as we do for the tree root and the…
When was CVE-2026-46251 disclosed?
CVE-2026-46251 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46251 actively exploited?
CVE-2026-46251 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-46251?
CVE-2026-46251 has a CVSS v4.0 base score of 8.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46251?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46251, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46251

Explore →

Is Your Infrastructure Affected by CVE-2026-46251?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs