Поиск уязвимостей
Количество 24
Количество 24
CVE-2025-37772
In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: ==========...
CVE-2025-37772
In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: ==========...
CVE-2025-37772
In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: =======
CVE-2025-37772
RDMA/cma: Fix workqueue crash in cma_netevent_work_handler
CVE-2025-37772
In the Linux kernel, the following vulnerability has been resolved: R ...
GHSA-frjr-3w6j-qh2v
In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: ====...
BDU:2025-12158
Уязвимость компонента RDMA/cma ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260126-80-0074
Уязвимость kernel-lt
ROS-20260126-73-0052
Уязвимость kernel-lt
SUSE-SU-2025:02000-1
Security update for the Linux Kernel
SUSE-SU-2025:01965-1
Security update for the Linux Kernel
ALT-PU-2025-16507
ALT-PU-2025-16507: package `kernel-image-6.12` update to version 6.12.27-alt1
ALT-PU-2025-16463
ALT-PU-2025-16463: package `kernel-image-rt` update to version 6.12.27-alt1
ALT-PU-2025-6032
ALT-PU-2025-6032: package `kernel-image-pine` update to version 6.12.25-alt1
SUSE-SU-2025:02333-1
Security update for the Linux Kernel
SUSE-SU-2025:02307-1
Security update for the Linux Kernel
SUSE-SU-2025:02254-1
Security update for the Linux Kernel
SUSE-SU-2025:01964-1
Security update for the Linux Kernel
ALT-PU-2025-7195
ALT-PU-2025-7195: package `kernel-image-un-def` update to version 6.1.140-alt1
SUSE-SU-2025:02923-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-37772 In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: ==========... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-37772 In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: ==========... | 0% Низкий | больше 1 года назад | ||
CVE-2025-37772 In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: ======= | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-37772 RDMA/cma: Fix workqueue crash in cma_netevent_work_handler | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-37772 In the Linux kernel, the following vulnerability has been resolved: R ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
GHSA-frjr-3w6j-qh2v In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix workqueue crash in cma_netevent_work_handler struct rdma_cm_id has member "struct work_struct net_work" that is reused for enqueuing cma_netevent_work_handler()s onto cma_wq. Below crash[1] can occur if more than one call to cma_netevent_callback() occurs in quick succession, which further enqueues cma_netevent_work_handler()s for the same rdma_cm_id, overwriting any previously queued work-item(s) that was just scheduled to run i.e. there is no guarantee the queued work item may run between two successive calls to cma_netevent_callback() and the 2nd INIT_WORK would overwrite the 1st work item (for the same rdma_cm_id), despite grabbing id_table_lock during enqueue. Also drgn analysis [2] indicates the work item was likely overwritten. Fix this by moving the INIT_WORK() to __rdma_create_id(), so that it doesn't race with any existing queue_work() or its worker thread. [1] Trimmed crash stack: ====... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
BDU:2025-12158 Уязвимость компонента RDMA/cma ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20260126-80-0074 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
ROS-20260126-73-0052 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
SUSE-SU-2025:02000-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01965-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-16507 ALT-PU-2025-16507: package `kernel-image-6.12` update to version 6.12.27-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2025-16463 ALT-PU-2025-16463: package `kernel-image-rt` update to version 6.12.27-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2025-6032 ALT-PU-2025-6032: package `kernel-image-pine` update to version 6.12.25-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
SUSE-SU-2025:02333-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:02307-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:02254-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01964-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-7195 ALT-PU-2025-7195: package `kernel-image-un-def` update to version 6.1.140-alt1 | CVSS3: 9.8 | больше 1 года назад | ||
SUSE-SU-2025:02923-1 Security update for the Linux Kernel | около 1 года назад |
Уязвимостей на страницу