Kernel warning via stale ext4 disk size
Published Feb 26, 2025 · Updated May 11, 2026
State inconsistency in Linux kernel ext4 allows local users to trigger a kernel warning through an inode resize and direct write. ext4_setattr updates i_disksize before ext4_mark_inode_dirty succeeds and fails to restore the old value when inode-block allocation returns ENOMEM, leaving i_size and i_disksize inconsistent. Triggering the warning requires access to resize and directly write an ext4 inode after the allocation failure; panic_on_warn converts the warning into a kernel panic.
Summary
What happened
State inconsistency in Linux kernel ext4 allows local users to trigger a kernel warning through an inode resize and direct write. ext4_setattr updates i_disksize before ext4_mark_inode_dirty succeeds and fails to restore the old value when inode-block allocation returns ENOMEM, leaving i_size and i_disksize inconsistent. Triggering the warning requires access to resize and directly write an ext4 inode after the allocation failure; panic_on_warn converts the warning into a kernel panic.
The record
- CVE
- CVE-2022-49352
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 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=5.5
- Affected versionversion=b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 <1bcce88da60eccc946c0f4ed942b0f08cd565778
- Affected versionversion=b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 <adf490083ca52ebfb0b2fe64ff1ead00c0452dd7
- Affected versionversion=b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 <b81d2ff6885e38fc745eeaf9565775055778fc0b
- Affected versionversion=b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 <e383c2aa5f02ab571530dc5c5696479672478c25
- Affected versionversion=b1b4705d54abedfd69dcdf42779c521aa1e0fbd3 <f4534c9fc94d22383f187b9409abb3f9df2e3db3
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