Memory exhaustion via unreleased ext4 extent path
Published May 27, 2026 · Updated May 27, 2026
Memory leak in the ext4 extent-shifting code in affected Linux Kernel releases allows local users to exhaust kernel memory. When ext4_ext_shift_extents() encounters a null extent, it returns without releasing the path allocated by ext4_find_extent(). A local low-privileged user must reach the ext4 extent-shift operation; repeated triggering consumes kernel memory and can interrupt the system without affecting confidentiality or integrity.
Summary
What happened
Memory leak in the ext4 extent-shifting code in affected Linux Kernel releases allows local users to exhaust kernel memory. When ext4_ext_shift_extents() encounters a null extent, it returns without releasing the path allocated by ext4_find_extent(). A local low-privileged user must reach the ext4 extent-shift operation; repeated triggering consumes kernel memory and can interrupt the system without affecting confidentiality or integrity.
The record
- CVE
- CVE-2026-45948
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.001
- 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=3.15
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <12615ab4bfb69678e5d961b28bb70040299e51b1
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <1bce219ee5512cf179ba40cf114945a14a16e21f
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <2f4b1052246ca646bb17bfe0f53df2fdf9729b58
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <4a79fde8db7eba7f1128d971ceba4e3c9ac84aec
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <7e807cb8603b7664fa630a696cd891d9a03c248d
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <afc5e61e1a07b2b833bd72cbee36ecce9cd901e2
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <bd7b52557e4a3ccd7595fdb3a585f1257de57935
- Affected versionversion=a18ed359bdddcded4f97ff5e2f07793ff9336913 <ca81109d4a8f192dc1cbad4a1ee25246363c2833
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