CVE-2024-50015
Linux Kernel Ext4 DAX Inode Size Underflow Vulnerability
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.
INFO
Published Date :
Oct. 21, 2024, 7:15 p.m.
Last Modified :
Oct. 28, 2024, 5:13 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-50015.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-50015 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-50015 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Oct. 28, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d No Types Assigned https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d Patch Changed Reference Type https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 No Types Assigned https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 Patch Changed Reference Type https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 No Types Assigned https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 Patch Changed Reference Type https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c No Types Assigned https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c Patch Changed Reference Type https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e No Types Assigned https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e Patch Changed Reference Type https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 No Types Assigned https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 Patch Changed Reference Type https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 No Types Assigned https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 Patch Added CWE NIST NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.10 up to (excluding) 5.10.227 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.168 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.113 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.55 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.11 up to (excluding) 6.11.3 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 21, 2024
Action Type Old Value New Value Added 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. Added Reference kernel.org https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-50015 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-50015
weaknesses.