Поиск уязвимостей
Количество 20
Количество 20
CVE-2024-26696
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause i...
CVE-2024-26696
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause i...
CVE-2024-26696
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause
CVE-2024-26696
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-cwr2-26gq-v2xr
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root ca...
ROS-20241016-02
Множественные уязвимости kernel-lt
ALT-PU-2024-2868
ALT-PU-2024-2868: package `kernel-image-un-def` update to version 6.1.79-alt1
ALT-PU-2024-18361
ALT-PU-2024-18361: package `kernel-image-std-def` update to version 6.1.79-alt1
ALT-PU-2024-3144
ALT-PU-2024-3144: package `kernel-image-rt` update to version 6.1.79-alt1.rt25
ALT-PU-2024-18464
ALT-PU-2024-18464: package `kernel-image-un-def` update to version 6.6.18-alt1
ALT-PU-2024-18207
ALT-PU-2024-18207: package `kernel-image-pine` update to version 6.6.18-alt1
ALT-PU-2024-3273
ALT-PU-2024-3273: package `kernel-image-rt` update to version 5.10.210-alt1.rt102
SUSE-SU-2024:1490-1
Security update for the Linux Kernel
ALT-PU-2024-3457
ALT-PU-2024-3457: package `kernel-image-std-def` update to version 5.10.211-alt1
SUSE-SU-2024:1659-1
Security update for the Linux Kernel
SUSE-SU-2024:1663-1
Security update for the Linux Kernel
ALT-PU-2024-3415
ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1
SUSE-SU-2024:2135-1
Security update for the Linux Kernel
ALT-PU-2024-6818
ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1
ALT-PU-2024-14046
ALT-PU-2024-14046: package `kernel-image-rpi-un` update to version 6.6.56-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26696 In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause i... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26696 In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause i... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26696 In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root cause | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26696 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
GHSA-cwr2-26gq-v2xr In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/pages in the middle of writeback will be updated and become dirty. Nilfs2 adds a checksum to verify the validity of the log being written and uses it for recovery at mount, so data changes during writeback are suppressed. Since this is broken, an unclean shutdown could potentially cause recovery to fail. Investigation revealed that the root ca... | CVSS3: 5.5 | 0% Низкий | больше 2 лет назад | |
ROS-20241016-02 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-2868 ALT-PU-2024-2868: package `kernel-image-un-def` update to version 6.1.79-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18361 ALT-PU-2024-18361: package `kernel-image-std-def` update to version 6.1.79-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-3144 ALT-PU-2024-3144: package `kernel-image-rt` update to version 6.1.79-alt1.rt25 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18464 ALT-PU-2024-18464: package `kernel-image-un-def` update to version 6.6.18-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-18207 ALT-PU-2024-18207: package `kernel-image-pine` update to version 6.6.18-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
ALT-PU-2024-3273 ALT-PU-2024-3273: package `kernel-image-rt` update to version 5.10.210-alt1.rt102 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:1490-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-3457 ALT-PU-2024-3457: package `kernel-image-std-def` update to version 5.10.211-alt1 | CVSS3: 9.8 | больше 2 лет назад | ||
SUSE-SU-2024:1659-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1663-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-3415 ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1 | CVSS3: 9.4 | больше 2 лет назад | ||
SUSE-SU-2024:2135-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2024-6818 ALT-PU-2024-6818: package `kernel-image-rpi-un` update to version 6.6.23-alt1 | CVSS3: 9.4 | больше 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 года назад |
Уязвимостей на страницу