Skip to content
Infrastructure

CVE-2026-46251

8.4
High
EPSS 0.13%Patch availableJun 5, 2026

Linux kernel Btrfs: block_group_tree list corruption in EXTENT_TREE_V2 path.

common questions

Is CVE-2026-46251 being exploited?

Not confirmed. CVE-2026-46251 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-46251?

CVE-2026-46251 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46251?

Yes. A fix has been recorded for CVE-2026-46251. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46251 affect?

CVE-2026-46251 affects Linux kernel (Btrfs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46251?

Apply kernel update with the Btrfs fix; reboot and verify FS integrity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (Btrfs)
impact

Btrfs block_group_tree corruption can cause transaction aborts and data integrity issues.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 14033b08a02916e85ffc5397e4ac15337359f3ae and < 6e10283b5519d987d880d71bec90cdc7f2ec62b3
  • affected>= 14033b08a02916e85ffc5397e4ac15337359f3ae and < e3d1fd084319f8f0830b22f014c7af6a96b4497b
  • affected>= 14033b08a02916e85ffc5397e4ac15337359f3ae and < 4eb830847d84276f1c8ea46541cfeeedaba1fb63
  • affected>= 14033b08a02916e85ffc5397e4ac15337359f3ae and < 80e1fda9c084dcf54819a12bc7682ec0afd2d8f4
  • affected>= 14033b08a02916e85ffc5397e4ac15337359f3ae and < 201091da34c4f113af6b4a7407091c39bf29d4ca
  • affected>= 14033b08a02916e85ffc5397e4ac15337359f3ae and < 3a1f4264daed4b419c325a7fe35e756cada3cf82
  • affecteddabf41db56f378a360ff0219c467f8dfecda7dd6
  • affected>= 6.0.19 and < 6.1
  • affected6.1
vendor says fixed in< 6.1, >= 6.1.165 and <= 6.1.*, >= 6.6.128 and <= 6.6.*, >= 6.12.75 and <= 6.12.*, >= 6.18.14 and <= 6.18.*, >= 6.19.4 and <= 6.19.*, >= 7.0 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free