Kernel warning via stale ext4 i_disksize
Published May 2, 2025 · Updated May 11, 2026
Improper bootloader-inode initialization in Linux 3.10 through 6.3-rc1 allows local users to trigger a kernel warning through ext4. The EXT4_IOC_SWAP_BOOT initialization path clears i_size but leaves a preexisting nonzero i_disksize, so a later direct write reaches an invariant check in ext4_file_write_iter. Exploitation requires local low-privileged access, a mounted corrupted ext4 image, and use of the ioctl; the demonstrated consequence is a kernel warning during write.
Summary
What happened
Improper bootloader-inode initialization in Linux 3.10 through 6.3-rc1 allows local users to trigger a kernel warning through ext4. The EXT4_IOC_SWAP_BOOT initialization path clears i_size but leaves a preexisting nonzero i_disksize, so a later direct write reaches an invariant check in ext4_file_write_iter. Exploitation requires local low-privileged access, a mounted corrupted ext4 image, and use of the ioctl; the demonstrated consequence is a kernel warning during write.
The record
- CVE
- CVE-2023-53101
- Published
- May 2, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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.10
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <01a821aacc64d4b05dafd239dbc9b7856686002f
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <0d8a6c9a6415999fee1259ccf1796480c026b7d6
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <3f00c476da8fe7c4c34ea16abb55d74127120413
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <59eee0cdf8c036f554add97a4da7c06d7a9ff34a
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <9cb27b1e76f0cc886ac09055bc41c0ab3f205167
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <9e9a4cc5486356158554f6ad73027d8635a48b34
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <d6c1447e483c05dbcfb3ff77ac04237a82070b8c
- Affected versionversion=393d1d1d76933886d5e1ce603214c9987589c6d5 <f5361da1e60d54ec81346aee8e3d8baf1be0b762
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.
Weakness, pattern, technique
No sourced classifications are available.
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