Поиск уязвимостей
Количество 29
Количество 29
CVE-2024-26846
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too.
CVE-2024-26846
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too.
CVE-2024-26846
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too.
CVE-2024-26846
In the Linux kernel, the following vulnerability has been resolved: n ...
GHSA-mvgr-2rgh-283w
In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too.
BDU:2024-09163
Уязвимость компонента nvme-fc ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20241025-02
Множественные уязвимости kernel-lt
ALT-PU-2024-18074
ALT-PU-2024-18074: package `kernel-image-rt` update to version 5.10.211-alt1.rt103
ALT-PU-2024-18362
ALT-PU-2024-18362: package `kernel-image-std-def` update to version 6.1.80-alt1
ALT-PU-2024-18255
ALT-PU-2024-18255: package `kernel-image-rt` update to version 6.1.80-alt1.rt26
ALT-PU-2024-18055
ALT-PU-2024-18055: package `kernel-image-un-def` update to version 6.1.80-alt1
ALT-PU-2024-18465
ALT-PU-2024-18465: package `kernel-image-un-def` update to version 6.6.19-alt1
ALT-PU-2024-18208
ALT-PU-2024-18208: package `kernel-image-pine` update to version 6.6.20-alt1
ELSA-2024-7000
ELSA-2024-7000: kernel security update (IMPORTANT)
RLSA-2024:7000
Important: kernel security update
SUSE-SU-2024:1979-1
Security update for the Linux Kernel
SUSE-SU-2024:2184-1
Security update for the Linux Kernel
SUSE-SU-2024:1983-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
ALT-PU-2024-3415
ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-26846 In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too. | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26846 In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too. | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26846 In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too. | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
CVE-2024-26846 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
GHSA-mvgr-2rgh-283w In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be freed eventually. This makes calling ida_destroy unnecessary. We only have to ensure that all nvme_delete_ctrl code has been executed before we leave nvme_fc_exit_module. This is done by flushing the nvme_delete_wq workqueue. While at it, remove the unused nvme_fc_wq workqueue too. | CVSS3: 4.4 | 0% Низкий | больше 2 лет назад | |
BDU:2024-09163 Уязвимость компонента nvme-fc ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | почти 3 года назад | |
ROS-20241025-02 Множественные уязвимости kernel-lt | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-18074 ALT-PU-2024-18074: package `kernel-image-rt` update to version 5.10.211-alt1.rt103 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18362 ALT-PU-2024-18362: package `kernel-image-std-def` update to version 6.1.80-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18255 ALT-PU-2024-18255: package `kernel-image-rt` update to version 6.1.80-alt1.rt26 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18055 ALT-PU-2024-18055: package `kernel-image-un-def` update to version 6.1.80-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18465 ALT-PU-2024-18465: package `kernel-image-un-def` update to version 6.6.19-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ALT-PU-2024-18208 ALT-PU-2024-18208: package `kernel-image-pine` update to version 6.6.20-alt1 | CVSS3: 8.8 | больше 2 лет назад | ||
ELSA-2024-7000 ELSA-2024-7000: kernel security update (IMPORTANT) | около 2 лет назад | |||
RLSA-2024:7000 Important: kernel security update | больше 1 года назад | |||
SUSE-SU-2024:1979-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:2184-1 Security update for the Linux Kernel | больше 2 лет назад | |||
SUSE-SU-2024:1983-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 лет назад | ||
ALT-PU-2024-3415 ALT-PU-2024-3415: package `kernel-image-mp` update to version 6.7.8-alt1 | CVSS3: 9.4 | больше 2 лет назад |
Уязвимостей на страницу