In the Linux kernel, the following vulnerability has been resolved: btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps When… (CVE-2026-68442)
A vulnerability in the Linux kernel's btrfs filesystem was resolved involving improper handling of the EXTENT_FLAG_LOGGING flag during extent map splitting. The issue caused the flag to be incorrectly inherited by split extent maps, leading to a use-after-free condition when the extent map was freed while still referenced. This flaw was fixed by correctly clearing the EXTENT_FLAG_LOGGING flag in the local flags copy used for splits, restoring intended behavior.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's btrfs filesystem arises from a logic error in btrfs_drop_extent_map_range() where split extent maps inherit the EXTENT_FLAG_LOGGING flag incorrectly due to a change in how flags were cleared. This causes the flag to remain set on split maps, which when freed while still on the inode's modified_extents list, triggers a WARN_ON and leads to a use-after-free condition. The fix involves clearing EXTENT_FLAG_LOGGING from the local flags copy used during splitting and only clearing EXTENT_FLAG_PINNED from the actual extent map flags, restoring behavior prior to the problematic commit.
Potential Impact
This vulnerability can lead to a use-after-free condition in the btrfs filesystem code of the Linux kernel. Use-after-free bugs can cause kernel crashes or potentially allow attackers to execute arbitrary code or escalate privileges if exploited. However, no known exploits are reported in the wild for this issue at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by correcting the flag handling logic in btrfs_drop_extent_map_range(). Users should apply the official kernel updates that include this patch when available. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed here; users should consult the vendor or Linux kernel advisories for the exact fixed versions and update instructions.
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps When… (CVE-2026-68442)
Description
A vulnerability in the Linux kernel's btrfs filesystem was resolved involving improper handling of the EXTENT_FLAG_LOGGING flag during extent map splitting. The issue caused the flag to be incorrectly inherited by split extent maps, leading to a use-after-free condition when the extent map was freed while still referenced. This flaw was fixed by correctly clearing the EXTENT_FLAG_LOGGING flag in the local flags copy used for splits, restoring intended behavior.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's btrfs filesystem arises from a logic error in btrfs_drop_extent_map_range() where split extent maps inherit the EXTENT_FLAG_LOGGING flag incorrectly due to a change in how flags were cleared. This causes the flag to remain set on split maps, which when freed while still on the inode's modified_extents list, triggers a WARN_ON and leads to a use-after-free condition. The fix involves clearing EXTENT_FLAG_LOGGING from the local flags copy used during splitting and only clearing EXTENT_FLAG_PINNED from the actual extent map flags, restoring behavior prior to the problematic commit.
Potential Impact
This vulnerability can lead to a use-after-free condition in the btrfs filesystem code of the Linux kernel. Use-after-free bugs can cause kernel crashes or potentially allow attackers to execute arbitrary code or escalate privileges if exploited. However, no known exploits are reported in the wild for this issue at this time.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by correcting the flag handling logic in btrfs_drop_extent_map_range(). Users should apply the official kernel updates that include this patch when available. Since this is a kernel-level issue, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed here; users should consult the vendor or Linux kernel advisories for the exact fixed versions and update instructions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gr86-25pq-rhr2
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-68442"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7c9b69bf8831d539cdf6ab
Added to database: 08/12/2026, 16:12:25 UTC
Last enriched: 08/12/2026, 17:18:17 UTC
Last updated: 08/13/2026, 00:41:14 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.