Kernel memory corruption via ext4 path double-free
Published Oct 21, 2024 · Updated Aug 5, 2026
A double-free in Linux kernel ext4 fast-commit replay allows local users to corrupt kernel memory while replaying an extent update. ext4_ext_replay_update_ex passes a copied path pointer to ext4_force_split_extent_at; when ext4_find_extent frees and nulls that copy while growing the extent tree, the caller frees the stale original path again. Reaching the flaw requires local low-privileged access and an extent replay that grows the tree depth; the record does not specify a resulting crash or privilege gain.
Summary
What happened
A double-free in Linux kernel ext4 fast-commit replay allows local users to corrupt kernel memory while replaying an extent update. ext4_ext_replay_update_ex passes a copied path pointer to ext4_force_split_extent_at; when ext4_find_extent frees and nulls that copy while growing the extent tree, the caller frees the stale original path again. Reaching the flaw requires local low-privileged access and an extent replay that grows the tree depth; the record does not specify a resulting crash or privilege gain.
The record
- CVE
- CVE-2024-49983
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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=5.10
- Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <1b558006d98b7b0b730027be0ee98973dd10ee0d
- Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <3ff710662e8d86a63a39b334e9ca0cb10e5c14b0
- Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <5c0f4cc84d3a601c99bc5e6e6eb1cbda542cce95
- Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <6367d3f04c69e2b8770b8137bd800e0784b0abbc
- Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <63adc9016917e6970fb0104ee5fd6770f02b2d80
- Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <8c26d9e53e5fbacda0732a577e97c5a5b7882aaf
- Affected versionversion=8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 <a34bed978364114390162c27e50fca50791c568d
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
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