Поиск уязвимостей
Количество 24
Количество 24
CVE-2025-37920
In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp socket from ...
CVE-2025-37920
In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp socket from ...
CVE-2025-37920
In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp
CVE-2025-37920
xsk: Fix race condition in AF_XDP generic RX path
CVE-2025-37920
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-4qc6-52f6-6vgr
In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xd...
BDU:2026-03258
Уязвимость функции xsk_generic_rcv() модуля net/xdp/xsk.c ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
ROS-20260804-80-0043
Уязвимость kernel-lt
ROS-20260804-73-0042
Уязвимость kernel-lt
SUSE-SU-2025:02846-1
Security update for the Linux Kernel
ALT-PU-2025-16508
ALT-PU-2025-16508: package `kernel-image-6.12` update to version 6.12.29-alt1
ALT-PU-2025-16454
ALT-PU-2025-16454: package `kernel-image-pine` update to version 6.12.28-alt2
SUSE-SU-2025:03023-1
Security update for the Linux Kernel
SUSE-SU-2025:02996-1
Security update for the Linux Kernel
SUSE-SU-2025:02969-1
Security update for the Linux Kernel
SUSE-SU-2025:02853-1
Security update for the Linux Kernel
SUSE-SU-2025:02997-1
Security update for the Linux Kernel
SUSE-SU-2025:03011-1
Security update for the Linux Kernel
SUSE-SU-2025:02923-1
Security update for the Linux Kernel
ALT-PU-2025-8293
ALT-PU-2025-8293: package `kernel-image-rt` update to version 6.12.34-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2025-37920 In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp socket from ... | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
CVE-2025-37920 In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp socket from ... | CVSS3: 4.1 | 0% Низкий | больше 1 года назад | |
CVE-2025-37920 In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xdp | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
CVE-2025-37920 xsk: Fix race condition in AF_XDP generic RX path | CVSS3: 4.7 | 0% Низкий | около 1 года назад | |
CVE-2025-37920 In the Linux kernel, the following vulnerability has been resolved: x ... | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
GHSA-4qc6-52f6-6vgr In the Linux kernel, the following vulnerability has been resolved: xsk: Fix race condition in AF_XDP generic RX path Move rx_lock from xsk_socket to xsk_buff_pool. Fix synchronization for shared umem mode in generic RX path where multiple sockets share single xsk_buff_pool. RX queue is exclusive to xsk_socket, while FILL queue can be shared between multiple sockets. This could result in race condition where two CPU cores access RX path of two different sockets sharing the same umem. Protect both queues by acquiring spinlock in shared xsk_buff_pool. Lock contention may be minimized in the future by some per-thread FQ buffering. It's safe and necessary to move spin_lock_bh(rx_lock) after xsk_rcv_check(): * xs->pool and spinlock_init is synchronized by xsk_bind() -> xsk_is_bound() memory barriers. * xsk_rcv_check() may return true at the moment of xsk_release() or xsk_unbind_dev(), however this will not cause any data races or race conditions. xsk_unbind_dev() removes xd... | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
BDU:2026-03258 Уязвимость функции xsk_generic_rcv() модуля net/xdp/xsk.c ядра операционной системы Linux, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации | CVSS3: 7 | 0% Низкий | больше 1 года назад | |
ROS-20260804-80-0043 Уязвимость kernel-lt | CVSS3: 7 | 0% Низкий | 3 месяца назад | |
ROS-20260804-73-0042 Уязвимость kernel-lt | CVSS3: 7 | 0% Низкий | 3 месяца назад | |
SUSE-SU-2025:02846-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2025-16508 ALT-PU-2025-16508: package `kernel-image-6.12` update to version 6.12.29-alt1 | CVSS3: 8.8 | больше 1 года назад | ||
ALT-PU-2025-16454 ALT-PU-2025-16454: package `kernel-image-pine` update to version 6.12.28-alt2 | CVSS3: 8.8 | больше 1 года назад | ||
SUSE-SU-2025:03023-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02996-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02969-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02853-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02997-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:03011-1 Security update for the Linux Kernel | около 1 года назад | |||
SUSE-SU-2025:02923-1 Security update for the Linux Kernel | около 1 года назад | |||
ALT-PU-2025-8293 ALT-PU-2025-8293: package `kernel-image-rt` update to version 6.12.34-alt1 | CVSS3: 8.8 | больше 1 года назад |
Уязвимостей на страницу