ext4 Filesystem Extent Cache Corruption on Split Failure

Publication date: 2026-05-27

Last updated on: 2026-06-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: drop extent cache when splitting extent fails When the split extent fails, we might leave some extents still being processed and return an error directly, which will result in stale extent entries remaining in the extent status tree. So drop all of the remaining potentially stale extents if the splitting fails.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-27

Last Modified

2026-06-25

Generated

2026-07-06

AI Q&A

2026-05-27

EPSS Evaluated

2026-07-05

NVD

CVE-2026-45899

EUVD

EUVD-2026-32365

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.13 (inc) to 6.18.14 (exc)
linux	linux_kernel	From 6.19 (inc) to 6.19.4 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.75 (exc)
linux	linux_kernel	From 5.11 (inc) to 5.15.203 (exc)
linux	linux_kernel	From 3.12 (inc) to 5.10.253 (exc)
linux	linux_kernel	From 5.16 (inc) to 6.6.130 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's ext4 filesystem. When an operation to split an extent fails, some extents may remain in an inconsistent state because the system returns an error without properly clearing these extents. This results in stale extent entries remaining in the extent status tree, which can cause issues with filesystem integrity. The fix involves dropping all potentially stale extents if the splitting operation fails.

Impact Analysis

If this vulnerability is exploited or triggered, it can lead to stale or inconsistent extent entries in the ext4 filesystem's extent status tree. This may cause filesystem corruption or unexpected behavior when accessing files, potentially leading to data loss or system instability.

Hi! I’m here to help you understand CVE-2026-45899. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70