PatchSiren cyber security CVE debrief
CVE-2026-45858 Linux CVE debrief
A logic error in the Linux kernel's ext4 filesystem can expose stale data when splitting unwritten extents. When ext4_split_extent() fails to split an extent at point B due to temporary space constraints, it incorrectly marks the entire extent as written after zeroing, leaving stale data in the range 0 to A. A subsequent successful split at A then preserves this stale data as a written extent. The fix passes EXT4_EXT_DATA_PARTIAL_VALID1 during the first split attempt, preventing premature conversion to written status and ensuring proper unwritten extent handling across both split operations.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-27
- Original CVE updated
- 2026-06-25
- Advisory published
- 2026-05-27
- Advisory updated
- 2026-06-25
Who should care
Linux system administrators, cloud infrastructure operators, container platform maintainers, and organizations running workloads on ext4 filesystems with large file operations or databases that rely on extent-based storage allocation.
Technical summary
The vulnerability exists in fs/ext4/extents.c in the ext4_split_extent() and ext4_split_extent_at() functions. When allocating initialized blocks from large unwritten extents or splitting during end I/O conversion, a two-part split operation can fail at the first split point (B) due to temporary space constraints. The original code passed EXT4_EXT_DATA_ENTIRE_VALID1 with EXT4_EXT_MAY_ZEROOUT, causing the entire extent to be marked as written after zeroing B to N, leaving stale data in 0 to A. When the second split at A succeeds with EXT4_EXT_DATA_VALID2, this stale data remains as a written extent. The fix uses EXT4_EXT_DATA_PARTIAL_VALID1 for the first split, keeping the extent unwritten after zeroing and allowing proper handling in the subsequent split operation.
Defensive priority
high
Recommended defensive actions
- Apply kernel updates from your Linux distribution that include the referenced stable kernel commits
- Reboot systems after kernel update to ensure patched code is active
- Verify kernel version matches or exceeds fixed versions in stable kernel branches
- Monitor filesystem integrity on ext4 volumes that handle large unwritten extents
- Review application data handling for sensitive information that may have been at risk from stale data exposure
Evidence notes
CVE published 2026-05-27. Multiple stable kernel commits provided. No CVSS score or severity assigned by NVD at time of disclosure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-45858 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-45858
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-45858 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45858
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/1bf6974822d1dba86cf11b5f05498581cf3488a2
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/58ddae5d77b1db3a27b891c75a8fa120239ac092
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/7015fcf473796e1d2d876f241bd9e0c36f3d4eef
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d17857b4fb9ba5745b59be0ef38fd532991fccbf
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/d67c8ecf3d8fda9b8ef80e6f665d84b6d6ac9d88
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.