Kernel memory corruption via stale ext4 extent path
Published Oct 21, 2024 · Updated Aug 5, 2026
Use-after-free in the ext4 extent-splitting path in Linux allows local users to corrupt kernel memory through ordinary file I/O. The ext4_split_extent_at function retains a stale path after ext4_find_extent frees it and nulls the caller's path pointer on an allocation or I/O error, then dereferences the freed path. A local low-privileged user with write access to an ext4 file can trigger writeback and cause kernel memory disclosure, corruption, or a panic without user interaction.
Summary
What happened
Use-after-free in the ext4 extent-splitting path in Linux allows local users to corrupt kernel memory through ordinary file I/O. The ext4_split_extent_at function retains a stale path after ext4_find_extent frees it and nulls the caller's path pointer on an allocation or I/O error, then dereferences the freed path. A local low-privileged user with write access to an ext4 file can trigger writeback and cause kernel memory disclosure, corruption, or a panic without user interaction.
The record
- CVE
- CVE-2024-49884
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- 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=3.18
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <393a46f60ea4f249dc9d496d4eb2d542f5e11ade
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <448100a29395b0c8b4c42967155849fe0fbe808f
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <5d949ea75bb529ea6342e83465938a3b0ac51238
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <8fe117790b37c84c651e2bad9efc0e7fda73c0e3
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <915ac3630488af0ca194dc63b86d99802b4f6e18
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <a5401d4c3e2a3d25643c567d26e6de327774a2c9
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <c26ab35702f8cd0cdc78f96aa5856bfb77be798f
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <cafcc1bd62934547c76abf46c6d0d54f135006fe
- Affected versionversion=dfe5080939ea4686b3414b5d970a9b26733c57a4 <e52f933598b781d291b9297e39c463536da0e185
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