Поиск уязвимостей
Количество 22
Количество 22
CVE-2021-47192
In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop the sta...
CVE-2021-47192
In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop the sta...
CVE-2021-47192
In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop the
CVE-2021-47192
In the Linux kernel, the following vulnerability has been resolved: s ...
GHSA-f834-hvgh-g5v9
In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop t...
BDU:2024-09219
Уязвимость компонента scsi ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ALT-PU-2021-3380
ALT-PU-2021-3380: package `kernel-image-std-def` update to version 5.10.82-alt1
ALT-PU-2021-3469
ALT-PU-2021-3469: package `kernel-image-std-def` update to version 5.10.82-alt1
ROS-20241024-02
Множественные уязвимости kernel-lt
SUSE-SU-2024:1641-1
Security update for the Linux Kernel
ALT-PU-2021-3358
ALT-PU-2021-3358: package `kernel-image-un-def` update to version 5.15.5-alt1
ALT-PU-2021-4943
ALT-PU-2021-4943: package `kernel-image-std-kvm` update to version 5.10.85-alt1
ALT-PU-2021-3618
ALT-PU-2021-3618: package `kernel-image-rt` update to version 5.10.87-alt1.rt59
SUSE-SU-2024:2185-1
Security update for the Linux Kernel
SUSE-SU-2024:1644-1
Security update for the Linux Kernel
SUSE-SU-2024:1659-1
Security update for the Linux Kernel
SUSE-SU-2024:1663-1
Security update for the Linux Kernel
ALT-PU-2021-4935
ALT-PU-2021-4935: package `kernel-image-mp` update to version 5.15.8-alt1
ALT-PU-2021-3660
ALT-PU-2021-3660: package `kernel-image-un-def` update to version 5.15.11-alt2
ALT-PU-2022-1428
ALT-PU-2022-1428: package `kernel-image-rt` update to version 5.10.100-alt1.rt62
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2021-47192 In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop the sta... | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
CVE-2021-47192 In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop the sta... | CVSS3: 4.4 | 1% Низкий | больше 2 лет назад | |
CVE-2021-47192 In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop the | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
CVE-2021-47192 In the Linux kernel, the following vulnerability has been resolved: s ... | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
GHSA-f834-hvgh-g5v9 In the Linux kernel, the following vulnerability has been resolved: scsi: core: sysfs: Fix hang when device state is set via sysfs This fixes a regression added with: commit f0f82e2476f6 ("scsi: core: Fix capacity set to zero after offlinining device") The problem is that after iSCSI recovery, iscsid will call into the kernel to set the dev's state to running, and with that patch we now call scsi_rescan_device() with the state_mutex held. If the SCSI error handler thread is just starting to test the device in scsi_send_eh_cmnd() then it's going to try to grab the state_mutex. We are then stuck, because when scsi_rescan_device() tries to send its I/O scsi_queue_rq() calls -> scsi_host_queue_ready() -> scsi_host_in_recovery() which will return true (the host state is still in recovery) and I/O will just be requeued. scsi_send_eh_cmnd() will then never be able to grab the state_mutex to finish error handling. To prevent the deadlock move the rescan-related code to after we drop t... | CVSS3: 5.3 | 1% Низкий | больше 2 лет назад | |
BDU:2024-09219 Уязвимость компонента scsi ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 1% Низкий | почти 5 лет назад | |
ALT-PU-2021-3380 ALT-PU-2021-3380: package `kernel-image-std-def` update to version 5.10.82-alt1 | CVSS3: 9.8 | почти 5 лет назад | ||
ALT-PU-2021-3469 ALT-PU-2021-3469: package `kernel-image-std-def` update to version 5.10.82-alt1 | CVSS3: 9.8 | почти 5 лет назад | ||
ROS-20241024-02 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
SUSE-SU-2024:1641-1 Security update for the Linux Kernel | больше 2 лет назад | |||
ALT-PU-2021-3358 ALT-PU-2021-3358: package `kernel-image-un-def` update to version 5.15.5-alt1 | CVSS3: 9.3 | почти 5 лет назад | ||
ALT-PU-2021-4943 ALT-PU-2021-4943: package `kernel-image-std-kvm` update to version 5.10.85-alt1 | CVSS3: 9.8 | почти 5 лет назад | ||
ALT-PU-2021-3618 ALT-PU-2021-3618: package `kernel-image-rt` update to version 5.10.87-alt1.rt59 | CVSS3: 9.8 | почти 5 лет назад | ||
SUSE-SU-2024:2185-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1644-1 Security update for the Linux Kernel | больше 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-2021-4935 ALT-PU-2021-4935: package `kernel-image-mp` update to version 5.15.8-alt1 | CVSS3: 9.8 | почти 5 лет назад | ||
ALT-PU-2021-3660 ALT-PU-2021-3660: package `kernel-image-un-def` update to version 5.15.11-alt2 | CVSS3: 9.8 | почти 5 лет назад | ||
ALT-PU-2022-1428 ALT-PU-2022-1428: package `kernel-image-rt` update to version 5.10.100-alt1.rt62 | CVSS3: 9.8 | больше 4 лет назад |
Уязвимостей на страницу