Skip to main content

Linux Kernel CVE-2026-68442

| EUVDEUVD-2026-57050 HIGH
2026-08-12 Linux GHSA-gr86-25pq-rhr2
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Local-only vector is confirmed; AC:H reflects the timing race between extent map shrinker and logging required to trigger the UAF reliably.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 01:46 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.8 (HIGH)
Patch available
Aug 12, 2026 - 01:02 EUVD
CVE Published
Aug 12, 2026 - 00:07 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 12, 2026 - 00:07 cve.org
HIGH 7.8

DescriptionCVE.org

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.

AnalysisAI

Use-after-free in the Linux kernel's btrfs filesystem driver allows a low-privileged local user to cause kernel memory corruption with full system compromise potential. Introduced by a regression in commit f86f7a75e2fb, the btrfs extent map splitting code in btrfs_drop_extent_map_range() incorrectly propagates EXTENT_FLAG_LOGGING to child split maps, which are never cleared of this flag; when the extent map shrinker later frees such a map while it remains on the inode's modified_extents list, a use-after-free is triggered. No public exploit has been identified at time of analysis, but an EPSS of 16% signals elevated exploitation probability for a local kernel UAF affecting Linux 6.8 and later across multiple stable branches.

Technical ContextAI

The btrfs B-tree filesystem subsystem in the Linux kernel manages extent maps - internal kernel data structures (struct extent_map) that track file data placement on disk. The function btrfs_drop_extent_map_range() splits an existing extent map when a sub-range is dropped, initializing the new split maps from a local 'flags' copy of the original map's flags. Commit f86f7a75e2fb, which changed how compression type is encoded via extent map flags, inadvertently altered the EXTENT_FLAG_LOGGING clearing to target em->flags directly rather than the local 'flags' copy used to seed splits. This means any extent map currently being logged - and bearing EXTENT_FLAG_LOGGING - will have that flag inherited by both split halves. The flag is never subsequently cleared on the splits. When the kernel's extent map shrinker reclaims memory by freeing such a split map while it still resides on the inode's modified_extents linked list, the WARN_ON(!list_empty(&em->list)) assertion in btrfs_free_extent_map() fires, and the freed memory is subsequently accessed (use-after-free). Affected CPE: cpe:2.3:a:linux:linux. No formal CWE is assigned, but the root cause maps to CWE-416 (Use After Free) with a flag-lifetime management regression as the precipitating defect.

RemediationAI

Upgrade the Linux kernel to a patched stable release: 6.12.101, 6.18.42, 7.1.6, or 7.2-rc5, pulling from the upstream stable commits listed in the References section (https://git.kernel.org/stable/c/2a9246a424f45f33a1b8367052611ebe874868ad et al.). Distribution-specific updates should be applied as soon as vendor kernels incorporate these backports. If immediate patching is not feasible, the most effective compensating control is to restrict local interactive access to systems where btrfs is in use - the vulnerability is not remotely exploitable, so limiting shell access to trusted administrators eliminates the attack surface entirely. Migrating affected filesystems from btrfs to ext4 or xfs is a more disruptive but complete mitigation for workloads where btrfs features are not strictly required; this eliminates the vulnerable code path at the cost of filesystem migration downtime. Reducing memory pressure to lower extent map shrinker activity may reduce triggering frequency but does not eliminate the vulnerability and is not a reliable mitigation. No patch-free workaround that preserves btrfs operation is available.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-68442 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy