System crash via ext4 extent integer overflow
Published Mar 4, 2022 · Updated Aug 3, 2024
Integer overflow in Linux Kernel before 5.9 allows local users to crash the system by mounting a crafted ext4 filesystem image. The ext4 extent-cache path accepts unchecked journal-inode extents, then ext4_es_cache_extent computes lblk + len in 32 bits and triggers a kernel BUG on wraparound. Exploitation requires permission to mount an attacker-controlled filesystem and causes an availability-only system crash.
Summary
What happened
Integer overflow in Linux Kernel before 5.9 allows local users to crash the system by mounting a crafted ext4 filesystem image. The ext4 extent-cache path accepts unchecked journal-inode extents, then ext4_es_cache_extent computes lblk + len in 32 bits and triggers a kernel BUG on wraparound. Exploitation requires permission to mount an attacker-controlled filesystem and causes an availability-only system crash.
The record
- CVE
- CVE-2021-3428
- Published
- Mar 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-190, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=Affects linux kernel before v5.9.
What conditions does exploitation require?
What is affected?
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