Answer in brief
CVE-2026-45892 records a Medium severity (CVSS 5.5) vulnerability in ext4: drop extent cache after doing PARTIAL_VALID1 zeroout. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ddf854e59166533b0f46ba32cd6cd9aca3197d1b <28db4bfc6f82fd20e2aadb7fc162244109a4eb31 || >=58ddae5d77b1db3a27b891c75a8fa120239ac092 <f0931a5c17005a0c4fc35bd1a001245effc3354b || >=d17857b4fb9ba5745b59be0ef38fd532991fccbf <d8ee559fccdef713f058cfe5f2c03dc9b18be3b1 || >=d67c8ecf3d8fda9b8ef80e6f665d84b6d6ac9d88 <c2ee51d684adca7645e4aa74adca13f6750390bc || >=7015fcf473796e1d2d876f241bd9e0c36f3d4eef <a1b962a821e7a52d48212ae269b45808b4411267 || >=1bf6974822d1dba86cf11b5f05498581cf3488a2 <6d882ea3b0931b43530d44149b79fcd4ffc13030 | 28db4bfc6f82fd20e2aadb7fc162244109a4eb31, f0931a5c17005a0c4fc35bd1a001245effc3354b, d8ee559fccdef713f058cfe5f2c03dc9b18be3b1, c2ee51d684adca7645e4aa74adca13f6750390bc, a1b962a821e7a52d48212ae269b45808b4411267, 6d882ea3b0931b43530d44149b79fcd4ffc13030 |
| Linux/Linuxgeneric | >=6.1.167 <6.1.168 | 6.1.168 |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-45892 records a Medium severity (CVSS 5.5) vulnerability in ext4: drop extent cache after doing PARTIAL_VALID1 zeroout. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ddf854e59166533b0f46ba32cd6cd9aca3197d1b <28db4bfc6f82fd20e2aadb7fc162244109a4eb31 || >=58ddae5d77b1db3a27b891c75a8fa120239ac092 <f0931a5c17005a0c4fc35bd1a001245effc3354b || >=d17857b4fb9ba5745b59be0ef38fd532991fccbf <d8ee559fccdef713f058cfe5f2c03dc9b18be3b1 || >=d67c8ecf3d8fda9b8ef80e6f665d84b6d6ac9d88 <c2ee51d684adca7645e4aa74adca13f6750390bc || >=7015fcf473796e1d2d876f241bd9e0c36f3d4eef <a1b962a821e7a52d48212ae269b45808b4411267 || >=1bf6974822d1dba86cf11b5f05498581cf3488a2 <6d882ea3b0931b43530d44149b79fcd4ffc13030 | 28db4bfc6f82fd20e2aadb7fc162244109a4eb31, f0931a5c17005a0c4fc35bd1a001245effc3354b, d8ee559fccdef713f058cfe5f2c03dc9b18be3b1, c2ee51d684adca7645e4aa74adca13f6750390bc, a1b962a821e7a52d48212ae269b45808b4411267, 6d882ea3b0931b43530d44149b79fcd4ffc13030 |
| Linux/Linuxgeneric | >=6.1.167 <6.1.168 | 6.1.168 |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.