Service interruption via uncleared ext4 cache entries
Published May 27, 2026 · Updated May 27, 2026
Improper cache cleanup in Linux Kernel ext4 allows local users to interrupt service when an extent-split operation fails. The failure path in fs/ext4/extents.c returns before removing every processed range, leaving stale entries in the extent status tree. Low-privileged local access and an ext4 workload that reaches the split-error path are required; the documented consequence is limited to system instability and availability loss.
Summary
What happened
Improper cache cleanup in Linux Kernel ext4 allows local users to interrupt service when an extent-split operation fails. The failure path in fs/ext4/extents.c returns before removing every processed range, leaving stale entries in the extent status tree. Low-privileged local access and an ext4 workload that reaches the split-error path are required; the documented consequence is limited to system instability and availability loss.
The record
- CVE
- CVE-2026-45899
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.10.253
- Affected versionversion=0 <5.15.203
- Affected versionversion=0 <6.12.75
- Affected versionversion=0 <6.18.14
- Affected versionversion=0 <6.19.4
- Affected versionversion=0 <6.6.130
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <120c6bd7ca9d3e80a968b758cbb3fbd67570f132
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <31bf37cf53ede8145e2bc62da803d4506da92975
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <337506dc652383c80839edb8d8dcdd8ff2129b4f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e54f8dfee359bbd58086c883ea8cffd5312999d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <79b592e8f1b435796cbc2722190368e3e8ffd7a1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <808f3191498f300174523c54cab101e18795ae4e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <dc7c9b9d03a59a7fe483574531327e650a4b4adc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo