btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps
Summary
| CVE | CVE-2026-68442 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-12 00:17:44 UTC |
| Updated | 2026-08-12 00:17:44 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps
When btrfs_drop_extent_map_range() splits an extent map, the new split
maps inherit the original map's flags through a local 'flags' variable.
Commit f86f7a75e2fb ("btrfs: use the flags of an extent map to identify
the compression type") changed the EXTENT_FLAG_LOGGING clearing to
operate on em->flags instead of that local 'flags' copy, so a split of
an extent map that is currently being logged wrongly inherits
EXTENT_FLAG_LOGGING.
The flag is then never cleared on the split, and when it is freed while
still on the inode's modified_extents list (for example by the extent
map shrinker) it trips the WARN_ON(!list_empty(&em->list)) in
btrfs_free_extent_map() and leads to a use-after-free.
Clear EXTENT_FLAG_LOGGING from the local 'flags' copy used for the
splits and only clear EXTENT_FLAG_PINNED from em->flags, restoring the
behaviour prior to f86f7a75e2fb. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected f86f7a75e2fb5fd7d31d00eab8a392f97ba42ce9 2a9246a424f45f33a1b8367052611ebe874868ad git |
Not specified |
| CNA |
Linux |
Linux |
affected f86f7a75e2fb5fd7d31d00eab8a392f97ba42ce9 9304713b70e7e1450e3a76e758836fe5391bfa95 git |
Not specified |
| CNA |
Linux |
Linux |
affected f86f7a75e2fb5fd7d31d00eab8a392f97ba42ce9 0e465c63f103a5ce6849614d6bda048d70eebec8 git |
Not specified |
| CNA |
Linux |
Linux |
affected f86f7a75e2fb5fd7d31d00eab8a392f97ba42ce9 5eff4d5b17fa1950e80bfd1ba43dc0699e61a644 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.8 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.8 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.101 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.42 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.6 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc5 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/5eff4d5b17fa1950e80bfd1ba43dc0699e61a644 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2a9246a424f45f33a1b8367052611ebe874868ad |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9304713b70e7e1450e3a76e758836fe5391bfa95 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0e465c63f103a5ce6849614d6bda048d70eebec8 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.