Количество 21
Количество 21
BDU:2026-02675
Уязвимость функции cnic_cm_stop_bnx2x_hw() в модуле drivers/net/ethernet/broadcom/cnic.c драйвера сетевых адаптеров Ethernet Broadcom ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
CVE-2025-39945
In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (cl...
CVE-2025-39945
In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (cl...
CVE-2025-39945
In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (c
CVE-2025-39945
cnic: Fix use-after-free bugs in cnic_delete_task
CVE-2025-39945
In the Linux kernel, the following vulnerability has been resolved: c ...
GHSA-g7c3-fwjq-9g8f
In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0...
ELSA-2025-28049
ELSA-2025-28049: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2025-28048
ELSA-2025-28048: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2025-25754
ELSA-2025-25754: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2025:4189-1
Security update for the Linux Kernel
SUSE-SU-2025:4111-1
Security update for the Linux Kernel
SUSE-SU-2025:4128-1
Security update for the Linux Kernel
SUSE-SU-2025:4301-1
Security update for the Linux Kernel
SUSE-SU-2025:4140-1
Security update for the Linux Kernel
SUSE-SU-2025:4320-1
Security update for the Linux Kernel
SUSE-SU-2025:4141-1
Security update for the Linux Kernel
SUSE-SU-2025:4132-1
Security update for the Linux Kernel
SUSE-SU-2025:4057-1
Security update for the Linux Kernel
openSUSE-SU-2025:20081-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2026-02675 Уязвимость функции cnic_cm_stop_bnx2x_hw() в модуле drivers/net/ethernet/broadcom/cnic.c драйвера сетевых адаптеров Ethernet Broadcom ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 8 | 0% Низкий | 7 месяцев назад | |
CVE-2025-39945 In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (cl... | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад | |
CVE-2025-39945 In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (cl... | CVSS3: 5.8 | 0% Низкий | 6 месяцев назад | |
CVE-2025-39945 In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0 (c | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад | |
CVE-2025-39945 cnic: Fix use-after-free bugs in cnic_delete_task | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад | |
CVE-2025-39945 In the Linux kernel, the following vulnerability has been resolved: c ... | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад | |
GHSA-g7c3-fwjq-9g8f In the Linux kernel, the following vulnerability has been resolved: cnic: Fix use-after-free bugs in cnic_delete_task The original code uses cancel_delayed_work() in cnic_cm_stop_bnx2x_hw(), which does not guarantee that the delayed work item 'delete_task' has fully completed if it was already running. Additionally, the delayed work item is cyclic, the flush_workqueue() in cnic_cm_stop_bnx2x_hw() only blocks and waits for work items that were already queued to the workqueue prior to its invocation. Any work items submitted after flush_workqueue() is called are not included in the set of tasks that the flush operation awaits. This means that after the cyclic work items have finished executing, a delayed work item may still exist in the workqueue. This leads to use-after-free scenarios where the cnic_dev is deallocated by cnic_free_dev(), while delete_task remains active and attempt to dereference cnic_dev in cnic_delete_task(). A typical race condition is illustrated below: CPU 0... | CVSS3: 7.8 | 0% Низкий | 6 месяцев назад | |
ELSA-2025-28049 ELSA-2025-28049: Unbreakable Enterprise kernel security update (IMPORTANT) | 4 месяца назад | |||
ELSA-2025-28048 ELSA-2025-28048: Unbreakable Enterprise kernel security update (IMPORTANT) | 4 месяца назад | |||
ELSA-2025-25754 ELSA-2025-25754: Unbreakable Enterprise kernel security update (IMPORTANT) | 5 месяцев назад | |||
SUSE-SU-2025:4189-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2025:4111-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2025:4128-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2025:4301-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2025:4140-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2025:4320-1 Security update for the Linux Kernel | 4 месяца назад | |||
SUSE-SU-2025:4141-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2025:4132-1 Security update for the Linux Kernel | 5 месяцев назад | |||
SUSE-SU-2025:4057-1 Security update for the Linux Kernel | 5 месяцев назад | |||
openSUSE-SU-2025:20081-1 Security update for the Linux Kernel | 4 месяца назад |
Уязвимостей на страницу