Поиск уязвимостей
Количество 20
Количество 20
CVE-2024-50015
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 r...
CVE-2024-50015
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 r...
CVE-2024-50015
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_updat
CVE-2024-50015
ext4: dax: fix overflowing extents beyond inode size when partially writing
CVE-2024-50015
In the Linux kernel, the following vulnerability has been resolved: e ...
GHSA-r75j-q9wj-xrc3
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_up...
BDU:2025-07976
Уязвимость ядра операционной системы Linux, связанная с чрезмерным итерированием, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20250317-01
Множественные уязвимости kernel-lt
ALT-PU-2024-17944
ALT-PU-2024-17944: package `kernel-image-un-def` update to version 6.6.56-alt0.p11.1
ALT-PU-2024-14270
ALT-PU-2024-14270: package `kernel-image-std-def` update to version 5.10.227-alt1
ELSA-2024-12887
ELSA-2024-12887: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2024:4314-1
Security update for the Linux Kernel
SUSE-SU-2024:3984-1
Security update for the Linux Kernel
ALT-PU-2024-16172
ALT-PU-2024-16172: package `kernel-image-rt` update to version 5.10.229-alt1.rt121
ALT-PU-2024-14268
ALT-PU-2024-14268: package `kernel-image-un-def` update to version 6.1.113-alt1
ELSA-2025-6966
ELSA-2025-6966: kernel security update (MODERATE)
ALT-PU-2024-17924
ALT-PU-2024-17924: package `kernel-image-pine` update to version 6.10.14-alt1
SUSE-SU-2024:4387-1
Security update for the Linux Kernel
SUSE-SU-2024:4318-1
Security update for the Linux Kernel
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-50015 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 r... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-50015 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 r... | CVSS3: 4.4 | 0% Низкий | около 2 лет назад | |
CVE-2024-50015 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_updat | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2024-50015 ext4: dax: fix overflowing extents beyond inode size when partially writing | CVSS3: 5.5 | 0% Низкий | 9 месяцев назад | |
CVE-2024-50015 In the Linux kernel, the following vulnerability has been resolved: e ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
GHSA-r75j-q9wj-xrc3 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_up... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
BDU:2025-07976 Уязвимость ядра операционной системы Linux, связанная с чрезмерным итерированием, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
ROS-20250317-01 Множественные уязвимости kernel-lt | CVSS3: 8.8 | больше 1 года назад | ||
ALT-PU-2024-17944 ALT-PU-2024-17944: package `kernel-image-un-def` update to version 6.6.56-alt0.p11.1 | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2024-14270 ALT-PU-2024-14270: package `kernel-image-std-def` update to version 5.10.227-alt1 | CVSS3: 9.1 | около 2 лет назад | ||
ELSA-2024-12887 ELSA-2024-12887: Unbreakable Enterprise kernel security update (IMPORTANT) | почти 2 года назад | |||
SUSE-SU-2024:4314-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3984-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-16172 ALT-PU-2024-16172: package `kernel-image-rt` update to version 5.10.229-alt1.rt121 | CVSS3: 9.1 | почти 2 года назад | ||
ALT-PU-2024-14268 ALT-PU-2024-14268: package `kernel-image-un-def` update to version 6.1.113-alt1 | CVSS3: 9.1 | около 2 лет назад | ||
ELSA-2025-6966 ELSA-2025-6966: kernel security update (MODERATE) | больше 1 года назад | |||
ALT-PU-2024-17924 ALT-PU-2024-17924: package `kernel-image-pine` update to version 6.10.14-alt1 | CVSS3: 9.1 | около 2 лет назад | ||
SUSE-SU-2024:4387-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:4318-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2024-14046 ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1 | CVSS3: 9.8 | почти 2 года назад |
Уязвимостей на страницу