Kernel crash via stale extent-move accounting
Published Apr 3, 2024 · Updated Aug 5, 2026
Double-free in Linux kernel ext4 allows local users to crash affected systems through crafted extent moves followed by filesystem trim. The ext4_move_extents() loop leaves moved_len at zero after a partial success, so inode preallocations are not discarded and overlapping blocks are freed twice. Exploitation requires local low-privileged access to an ext4 filesystem and a later trim operation; the bounded consequence is a kernel crash.
Summary
What happened
Double-free in Linux kernel ext4 allows local users to crash affected systems through crafted extent moves followed by filesystem trim. The ext4_move_extents() loop leaves moved_len at zero after a partial success, so inode preallocations are not discarded and overlapping blocks are freed twice. Exploitation requires local low-privileged access to an ext4 filesystem and a later trim operation; the bounded consequence is a kernel crash.
The record
- CVE
- CVE-2024-26704
- Published
- Apr 3, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=3.18
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <2883940b19c38d5884c8626483811acf4d7e148f
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <55583e899a5357308274601364741a83e78d6ac4
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <559ddacb90da1d8786dd8ec4fd76bbfa404eaef6
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <afba9d11320dad5ce222ac8964caf64b7b4bedb1
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <afbcad9ae7d6d11608399188f03a837451b6b3a1
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <b4fbb89d722cbb16beaaea234b7230faaaf68c71
- Affected versionversion=fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a <d033a555d9a1cf53dbf3301af7199cc4a4c8f537
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.
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