CVE - CVE-2024-50015

CVE-ID
CVE-2024-50015	Learn more at National Vulnerability Database (NVD) • CVSS Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings • CPE Information
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // round 1 ext4_iomap_begin ext4_iomap_alloc // allocate 0~2M extents(written flag) dax_iomap_iter // copy 2M data iomap_iter // round 2 iomap_iter_advance iter->pos += iter->processed // iter->pos = 2M ext4_iomap_begin ext4_iomap_alloc // allocate 2~4M extents(written flag) dax_iomap_iter fatal_signal_pending done = iter->pos - iocb->ki_pos // done = 2M ext4_handle_inode_extension ext4_update_inode_size // inode size = 2M fsck reports: Inode 13, i_size is 2097152, should be 4194304. Fix? Fix the problem by truncating extents if the written length is smaller than expected.
References
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
MISC:https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d URL:https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d MISC:https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 URL:https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 MISC:https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 URL:https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 MISC:https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c URL:https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c MISC:https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e URL:https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e MISC:https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 URL:https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 MISC:https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 URL:https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669
Assigning CNA
kernel.org
Date Record Created
20241021	Disclaimer: The record creation date may reflect when the CVE ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20241021)
Votes (Legacy)

Comments (Legacy)

Proposed (Legacy)
N/A
This is an record on the CVE List, which provides common identifiers for publicly known cybersecurity vulnerabilities.
Search CVE Using Keywords: You can also search by reference using the CVE Reference Maps.
For More Information: CVE Request Web Form (select "Other" from dropdown)