ext4: convert inline data to extents when truncate exceeds inline size
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in 110d7ef602659ce4d7947c5480f7ca2779696aaf; From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in f53a5d9f32924bc2a810d2df243b7714da58b636; From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in c047332be7195833a5c5126816c2502df8269fe4; From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in 699bac4d4c951974d55b045c983d1de777215949; From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in 7920dcc571cef3d8aa9ee109c136125d61d41669; From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in 93cb2d103e5c707de0f7ad58a39b7f0fddc27aa6; From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in 07c1a31af18290054da3d18221b8bf58983c5d3a; From 67cf5b09a46f72e048501b84996f2f77bc42e947 · fixed in ed9356a30e59c7cc3198e7fc46cfedf3767b9b17
- Linux Linux
3.8
- KernelLinux
From 3.8.0 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.168; From 6.2.0 · fixed in 6.6.131; From 6.7.0 · fixed in 6.12.80; From 6.13.0 · fixed in 6.18.21; From 6.19.0 · fixed in 6.19.11
References 8
git.kernel.org
- stable/c/110d7ef602659ce4d7947c5480f7ca2779696aaf
- stable/c/f53a5d9f32924bc2a810d2df243b7714da58b636
- stable/c/c047332be7195833a5c5126816c2502df8269fe4
- stable/c/699bac4d4c951974d55b045c983d1de777215949
- stable/c/7920dcc571cef3d8aa9ee109c136125d61d41669
- stable/c/93cb2d103e5c707de0f7ad58a39b7f0fddc27aa6
- stable/c/07c1a31af18290054da3d18221b8bf58983c5d3a
- stable/c/ed9356a30e59c7cc3198e7fc46cfedf3767b9b17