CVE-2024-50015

  1. Yack CVE
  2. Vulnerabilities (CVE)
  3. CVE-2024-50015

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

I

n 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
Link Resource
https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d Patch
https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 Patch
https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 Patch
https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c Patch
https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e Patch
https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 Patch
https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 Patch
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
History

03 Nov 2025, 23:16

Type Values Removed Values Added
References
  • () https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html -

03 Nov 2025, 21:16

Type Values Removed Values Added
References
  • () https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html -

28 Oct 2024, 17:13

Type Values Removed Values Added
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d - () https://git.kernel.org/stable/c/5efccdee4a7d507a483f20f880b809cc4eaef14d - Patch
References () https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 - () https://git.kernel.org/stable/c/8c30a9a8610c314554997f86370140746aa35661 - Patch
References () https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 - () https://git.kernel.org/stable/c/a9f331f51515bdb3ebc8d0963131af367ef468f6 - Patch
References () https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c - () https://git.kernel.org/stable/c/abfaa876b948baaea4d14f21a1963789845c8b4c - Patch
References () https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e - () https://git.kernel.org/stable/c/dda898d7ffe85931f9cca6d702a51f33717c501e - Patch
References () https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 - () https://git.kernel.org/stable/c/ec0dd451e236c46e4858d53e9e82bae7797a7af5 - Patch
References () https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 - () https://git.kernel.org/stable/c/f8a7c342326f6ad1dfdb30a18dd013c70f5e9669 - Patch
CWE NVD-CWE-noinfo
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
First Time Linux
Linux linux Kernel

23 Oct 2024, 15:13

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: dax: se corrige el desbordamiento de extensiones más allá del tamaño del inodo al escribir parcialmente. Dax_iomap_rw() hace dos cosas en cada iteración: asigna bloques escritos y copia datos de usuario a bloques. Si el usuario finaliza el proceso (consulte el manejo de señales en dax_iomap_iter()), los datos copiados se devolverán y se agregarán al tamaño del inodo, lo que significa que la longitud de las extensiones escritas puede exceder el tamaño del inodo, entonces fsck fallará. Se proporciona un ejemplo como: dd if=/dev/urandom of=file bs=4M count=1 dax_iomap_rw iomap_iter // ronda 1 ext4_iomap_begin ext4_iomap_alloc // asignar 0~2M de extensiones (bandera escrita) dax_iomap_iter // copiar 2M de datos iomap_iter // ronda 2 iomap_iter_advance iter->pos += iter->processed // iter->pos = 2M ext4_iomap_begin ext4_iomap_alloc // asignar 2~4M de extensiones (bandera escrita) dax_iomap_iter fatal_signal_pending hecho = iter->pos - iocb->ki_pos // hecho = 2M ext4_handle_inode_extension ext4_update_inode_size // tamaño de inodo = 2M fsck informa: Inodo 13, i_size es 2097152, debería ser 4194304. ¿Solución? Solucione el problema truncando las extensiones si la longitud escrita es menor a la esperada.

21 Oct 2024, 19:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-10-21 19:15

Updated : 2025-11-03 23:16

NVD link : CVE-2024-50015

Mitre link : CVE-2024-50015

CVE.ORG link : CVE-2024-50015

JSON object : View

Products Affected

linux

CWE
NVD-CWE-noinfo