CVE-2026-45892

published 27 May 2026 · updated 8 Nov 2026

ext4: drop extent cache after doing PARTIAL_VALID1 zeroout

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 28db4bfc6f82fd20e2aadb7fc162244109a4eb31, Kernel 6d882ea3b0931b43530d44149b79fcd4ffc13030, Kernel f0931a5c17005a0c4fc35bd1a001245effc3354b and 4 more.

In the Linux kernel, the following vulnerability has been resolved: ext4: drop extent cache after doing PARTIAL_VALID1 zeroout When splitting an unwritten extent in the middle and converting it to initialized in ext4_split_extent() with the EXT4_EXT_MAY_ZEROOUT and EXT4_EXT_DATA_VALID2 flags set, it could leave a stale unwritten extent. Assume we have an unwritten file and buffered write in the middle of it without dioread_nolock enabled, it will allocate blocks as written extent. 0 A B N [UUUUUUUUUUUU] on-disk extent U: unwritten extent [UUUUUUUUUUUU] extent status tree [--DDDDDDDD--] D: valid data |<- ->| ----> this range needs to be initialized ext4_split_extent() first try to split this extent at B with EXT4_EXT_DATA_PARTIAL_VALID1 and EXT4_EXT_MAY_ZEROOUT flag set, but ext4_split_extent_at() failed to split this extent due to temporary lack of space. It zeroout B to N and leave the entire extent as unwritten. 0 A B N [UUUUUUUUUUUU] on-disk extent [UUUUUUUUUUUU] extent status tree [--DDDDDDDDZZ] Z: zeroed data ext4_split_extent() then try to split this extent at A with EXT4_EXT_DATA_VALID2 flag set. This time, it split successfully and leave an written extent from A to N. 0 A B N [UUWWWWWWWWWW] on-disk extent W: written extent [UUUUUUUUUUUU] extent status tree [--DDDDDDDDZZ] Finally ext4_map_create_blocks() only insert extent A to B to the extent status tree, and leave an stale unwritten extent in the status tree. 0 A B N [UUWWWWWWWWWW] on-disk extent W: written extent [UUWWWWWWWWUU] extent status tree [--DDDDDDDDZZ] Fix this issue by always cached extent status entry after zeroing out the second part.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=ddf854e59166533b0f46ba32cd6cd9aca3197d1b <28db4bfc6f82fd20e2aadb7fc162244109a4eb31, =6.1.167, >=1bf6974822d1dba86cf11b5f05498581cf3488a2 <6d882ea3b0931b43530d44149b79fcd4ffc13030, >=58ddae5d77b1db3a27b891c75a8fa120239ac092 <f0931a5c17005a0c4fc35bd1a001245effc3354b, >=6.1.167 <6.1.168, >=7015fcf473796e1d2d876f241bd9e0c36f3d4eef <a1b962a821e7a52d48212ae269b45808b4411267, >=d17857b4fb9ba5745b59be0ef38fd532991fccbf <d8ee559fccdef713f058cfe5f2c03dc9b18be3b1, >=d67c8ecf3d8fda9b8ef80e6f665d84b6d6ac9d88 <c2ee51d684adca7645e4aa74adca13f6750390bc28db4bfc6f82fd20e2aadb7fc162244109a4eb31, 6d882ea3b0931b43530d44149b79fcd4ffc13030, f0931a5c17005a0c4fc35bd1a001245effc3354b, 6.1.168, a1b962a821e7a52d48212ae269b45808b4411267, d8ee559fccdef713f058cfe5f2c03dc9b18be3b1, c2ee51d684adca7645e4aa74adca13f6750390bc
linux-kernel: Kernel>=6.1.167 <6.1.1686.1.168

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-45892 severity on Zeptric[![CVE-2026-45892](https://zeptric.io/badge/cve/CVE-2026-45892.svg)](https://zeptric.io/cve/CVE-2026-45892)