CVE-2026-46251

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2026-34113 (ENISA EUVD) · GHSA-c5jw-wr2h-vpj4 (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.4Exploit: None knownExposed services: Not assessed

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.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 3, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jun 5, 2026
Patch available.
Web page

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

https://git.kernel.org/stable/c/e3d1fd084319f8f0830b22f014c7af6a96b4497b
Web page

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

https://git.kernel.org/stable/c/80e1fda9c084dcf54819a12bc7682ec0afd2d8f4
Web page

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

https://git.kernel.org/stable/c/6e10283b5519d987d880d71bec90cdc7f2ec62b3
Web page

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

https://git.kernel.org/stable/c/4eb830847d84276f1c8ea46541cfeeedaba1fb63
Web page

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

https://git.kernel.org/stable/c/3a1f4264daed4b419c325a7fe35e756cada3cf82
Web page

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-11-01ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-11-01ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-11-01ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-11-01ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-11-01ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-11-01ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-11-01ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-11-01ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-11-01ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-11-01ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-11-01ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-11-01ubuntu
linuxKernel @ 6.1.165 (fixes >=6.1.0)—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 rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (104 versions)
  • every version up to 6.18.14-1: fixed in 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 10× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 333 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 233 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-46251?
CVE-2026-46251 is a high-severity vulnerability; its CVE record was published on June 3, 2026. 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…
When was the CVE record for CVE-2026-46251 published?
The CVE record for CVE-2026-46251 was published on June 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2026-46251 actively exploited?
CVE-2026-46251 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46251?
CVE-2026-46251 has a CVSS base score of 8.4 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-46251?
A fix for CVE-2026-46251 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46251 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs