Skip to main content

Linux Kernel EUVDEUVD-2026-32270

| CVE-2026-45985 MEDIUM
2026-05-27 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-qwcw-8jc7-8mhw
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.8 MEDIUM

AC:H reflects three required simultaneous conditions (dioread_nolock, ENOSPC during split, DIO write failure); C:L and I:L added given confirmed stale-data exposure and extent state inconsistency absent from vendor vector.

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

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 16, 2026 - 14:08 vuln.today
CVSS changed
Jun 16, 2026 - 14:07 NVD
5.5 (MEDIUM)
Patch available
May 27, 2026 - 19:46 EUVD
CVE Published
May 27, 2026 - 14:17 nvd
MEDIUM 5.5
CVE Published
May 27, 2026 - 14:17 nvd
UNKNOWN (no severity yet)

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

ext4: don't set EXT4_GET_BLOCKS_CONVERT when splitting before submitting I/O

When allocating blocks during within-EOF DIO and writeback with dioread_nolock enabled, EXT4_GET_BLOCKS_PRE_IO was set to split an existing large unwritten extent. However, EXT4_GET_BLOCKS_CONVERT was set when calling ext4_split_convert_extents(), which may potentially result in stale data issues.

Assume we have an unwritten extent, and then DIO writes the second half.

[UUUUUUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUUUUUU] extent status tree

|<- ->| ----> dio write this range First, ext4_iomap_alloc() call ext4_map_blocks() with EXT4_GET_BLOCKS_PRE_IO, EXT4_GET_BLOCKS_UNWRIT_EXT and EXT4_GET_BLOCKS_CREATE flags set. ext4_map_blocks() find this extent and call ext4_split_convert_extents() with EXT4_GET_BLOCKS_CONVERT and the above flags set.

Then, ext4_split_convert_extents() calls ext4_split_extent() with EXT4_EXT_MAY_ZEROOUT, EXT4_EXT_MARK_UNWRIT2 and EXT4_EXT_DATA_VALID2 flags set, and it calls ext4_split_extent_at() to split the second half with EXT4_EXT_DATA_VALID2, EXT4_EXT_MARK_UNWRIT1, EXT4_EXT_MAY_ZEROOUT and EXT4_EXT_MARK_UNWRIT2 flags set. However, ext4_split_extent_at() failed to insert extent since a temporary lack -ENOSPC. It zeroes out the first half but convert the entire on-disk extent to written since the EXT4_EXT_DATA_VALID2 flag set, but left the second half as unwritten in the extent status tree.

[0000000000SSSSSS] data S: stale data, 0: zeroed [WWWWWWWWWWWWWWWW] on-disk extent W: written extent [WWWWWWWWWWUUUUUU] extent status tree

Finally, if the DIO failed to write data to the disk, the stale data in the second half will be exposed once the cached extent entry is gone.

Fix this issue by not passing EXT4_GET_BLOCKS_CONVERT when splitting an unwritten extent before submitting I/O, and make ext4_split_convert_extents() to zero out the entire extent range to zero for this case, and also mark the extent in the extent status tree for consistency.

AnalysisAI

Stale data exposure in the Linux kernel's ext4 filesystem affects systems using the dioread_nolock mount option, triggered by a flag-handling logic error in the extent-splitting code path during Direct I/O operations. When EXT4_GET_BLOCKS_CONVERT is incorrectly passed during a pre-I/O split of an unwritten extent, a simultaneous -ENOSPC failure in ext4_split_extent_at() causes the entire on-disk extent to be prematurely converted to written state while the in-memory extent status tree retains an inconsistent unwritten marker for the second half; if the DIO write subsequently fails, a future read of that region exposes stale pre-zero data. No public exploit has been identified at time of analysis, EPSS is 0.02% (7th percentile), and there is no CISA KEV listing, indicating no confirmed active exploitation.

Technical ContextAI

The affected subsystem is ext4's extent management layer within the Linux kernel, specifically the ext4_iomap_alloc()ext4_map_blocks()ext4_split_convert_extents() call chain invoked when dioread_nolock is active. The CPE cpe:2.3:o:linux:linux_kernel:* covers all affected kernel versions. The root cause is an incorrect flag assignment: EXT4_GET_BLOCKS_CONVERT is passed alongside EXT4_GET_BLOCKS_PRE_IO during an extent pre-split, which propagates EXT4_EXT_DATA_VALID2 into ext4_split_extent(). This flag signals that the trailing half of the split extent already contains valid data, bypassing the zeroing guard. When ext4_split_extent_at() hits a transient -ENOSPC mid-operation, its recovery path zeroes the first half but converts the full on-disk extent to written status - while the extent status tree (in-memory cache) is left recording the second half as unwritten. NVD did not assign a CWE, but the flaw maps closest to CWE-665 (Improper Initialization) or CWE-362 (Race Condition) due to incorrect state transition under a failure path.

RemediationAI

The primary remediation is upgrading to a patched Linux kernel: 5.10.253, 5.15.203, 6.6.130, 6.12.77, 6.18.17, 6.19.4, or 7.0. Patch commits are available at https://git.kernel.org/stable/c/2698731d25823267c29190cb578da9296a0c0d7b, https://git.kernel.org/stable/c/2920ec61c98b9476781359f05b94da84e80f54d4, https://git.kernel.org/stable/c/feaf2a80e78f89ee8a3464126077ba8683b62791, and related stable refs linked in NVD. For systems where immediate kernel upgrade is operationally infeasible, the most effective compensating control is remounting affected ext4 filesystems without dioread_nolock using 'mount -o remount,nodioread_nolock /mountpoint' and updating /etc/fstab accordingly; this fully disables the vulnerable code path at the cost of reduced Direct I/O write throughput for O_DIRECT workloads, which may be significant for database applications. No generic network-layer mitigations are applicable given the local-only attack vector. The NVD advisory is at https://nvd.nist.gov/vuln/detail/CVE-2026-45985.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Performance Computing 15 SP7 Affected

Share

EUVD-2026-32270 vulnerability details – vuln.today

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