Поиск уязвимостей
Количество 28
Количество 28
BDU:2025-12170
Уязвимость компонента RDMA/mlx5 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ROS-20260126-80-0006
Уязвимость kernel-lt
ROS-20260126-73-0002
Уязвимость kernel-lt
CVE-2025-22086
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D...
CVE-2025-22086
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D...
CVE-2025-22086
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD
CVE-2025-22086
RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow
CVE-2025-22086
In the Linux kernel, the following vulnerability has been resolved: R ...
GHSA-2q2c-9vgr-84gw
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page ...
ALT-PU-2025-16453
ALT-PU-2025-16453: package `kernel-image-pine` update to version 6.12.23-alt2
ALT-PU-2025-6606
ALT-PU-2025-6606: package `kernel-image-rt` update to version 5.10.237-alt1.rt131
ALT-PU-2025-6382
ALT-PU-2025-6382: package `kernel-image-std-def` update to version 5.10.237-alt1
ALT-PU-2025-5774
ALT-PU-2025-5774: package `kernel-image-6.12` update to version 6.12.24-alt1
ALT-PU-2025-7195
ALT-PU-2025-7195: package `kernel-image-un-def` update to version 6.1.140-alt1
ELSA-2025-20372
ELSA-2025-20372: Unbreakable Enterprise kernel security update (IMPORTANT)
ALT-PU-2025-5786
ALT-PU-2025-5786: package `kernel-image-rt` update to version 6.12.24-alt1
SUSE-SU-2025:01600-1
Security update for the Linux Kernel
SUSE-SU-2025:01972-1
Security update for the Linux Kernel
SUSE-SU-2025:01707-1
Security update for the Linux Kernel
SUSE-SU-2025:01614-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2025-12170 Уязвимость компонента RDMA/mlx5 ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ROS-20260126-80-0006 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
ROS-20260126-73-0002 Уязвимость kernel-lt | CVSS3: 5.5 | 0% Низкий | 10 месяцев назад | |
CVE-2025-22086 In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-22086 In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-22086 In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-22086 RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
CVE-2025-22086 In the Linux kernel, the following vulnerability has been resolved: R ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
GHSA-2q2c-9vgr-84gw In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page ... | CVSS3: 5.5 | 0% Низкий | больше 1 года назад | |
ALT-PU-2025-16453 ALT-PU-2025-16453: package `kernel-image-pine` update to version 6.12.23-alt2 | CVSS3: 9.8 | больше 1 года назад | ||
ALT-PU-2025-6606 ALT-PU-2025-6606: package `kernel-image-rt` update to version 5.10.237-alt1.rt131 | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2025-6382 ALT-PU-2025-6382: package `kernel-image-std-def` update to version 5.10.237-alt1 | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2025-5774 ALT-PU-2025-5774: package `kernel-image-6.12` update to version 6.12.24-alt1 | CVSS3: 9.8 | больше 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 года назад | ||
ELSA-2025-20372 ELSA-2025-20372: Unbreakable Enterprise kernel security update (IMPORTANT) | больше 1 года назад | |||
ALT-PU-2025-5786 ALT-PU-2025-5786: package `kernel-image-rt` update to version 6.12.24-alt1 | CVSS3: 9.8 | больше 1 года назад | ||
SUSE-SU-2025:01600-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01972-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01707-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01614-1 Security update for the Linux Kernel | больше 1 года назад |
Уязвимостей на страницу