Local system crash via ext4 journal replay
Published May 2, 2025 · Updated May 23, 2026
A NULL pointer dereference in the ext4 subsystem of Linux allows local users to crash the system by mounting a crafted filesystem image. During journal replay, a modified s_journal_inum value bypasses ext4_get_journal checks and leaves a NULL journal pointer that is later dereferenced. Exploitation requires local privileges sufficient to mount an attacker-controlled ext4 image, and the documented consequence is an availability-only system crash.
Summary
What happened
A NULL pointer dereference in the ext4 subsystem of Linux allows local users to crash the system by mounting a crafted filesystem image. During journal replay, a modified s_journal_inum value bypasses ext4_get_journal checks and leaves a NULL journal pointer that is later dereferenced. Exploitation requires local privileges sufficient to mount an attacker-controlled ext4 image, and the documented consequence is an availability-only system crash.
The record
- CVE
- CVE-2023-53091
- Published
- May 2, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=2fd4629de51974002f4e9cf1a35a1926dd6c9d99
- Affected versionversion=3.16.85 <3.17
- Affected versionversion=345c0dbf3a30872d9b204db96b5857cd00808cae <3039d8b8692408438a618fac2776b629852663c3
- Affected versionversion=345c0dbf3a30872d9b204db96b5857cd00808cae <499fef2030fb754c68b1c7cb3a799a3bc1d0d925
- Affected versionversion=345c0dbf3a30872d9b204db96b5857cd00808cae <70e66bdeae4d0f7c8e87762f425b68aedd5e8955
- Affected versionversion=345c0dbf3a30872d9b204db96b5857cd00808cae <ee0c5277d4fab920bd31345c49e193ecede9ecef
- Affected versionversion=4.14.178 <4.15
- Affected versionversion=4.19.73 <4.20
- Affected versionversion=4.4.221 <4.5
- Affected versionversion=4.9.221 <4.10
- Affected versionversion=51890201da4d654f6ca131bc45a0e892bb10de1d
- Affected versionversion=5.2
- Affected versionversion=795762468125a6412c089651e74f780bee154118
- Affected versionversion=7eff961ca9f364be255d279346517ba0158ec8e3
- Affected versionversion=a9855260fe8d8680bf8c4f0d8303b696c861e99b
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