Количество 24
Количество 24
CVE-2026-64268
In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so the p...
CVE-2026-64268
In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so the p...
CVE-2026-64268
In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so the p
CVE-2026-64268
RDMA/siw: bound Read Response placement to the RREAD length
CVE-2026-64268
In the Linux kernel, the following vulnerability has been resolved: R ...
ROS-20261014-80-0201
Уязвимость kernel-lt
ROS-20261014-73-0200
Уязвимость kernel-lt
GHSA-86rp-m36j-7r28
In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so th...
RLSA-2026:63014
Important: kernel security, bug fix, and enhancement update
ELSA-2026-63014-0
ELSA-2026-63014-0: kernel security, bug fix, and enhancement update (IMPORTANT)
RLSA-2026:63129
Important: kernel security, bug fix, and enhancement update
ELSA-2026-63129-0
ELSA-2026-63129-0: kernel security, bug fix, and enhancement update (IMPORTANT)
SUSE-SU-2026:4595-1
Security update for the Linux Kernel
ALT-PU-2026-11928
ALT-PU-2026-11928: package `kernel-image-std-def` update to version 5.10.262-alt1
SUSE-SU-2026:4284-1
Security update for the Linux Kernel
ALT-PU-2026-11926
ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1
SUSE-SU-2026:4369-1
Security update for the Linux Kernel
ALT-PU-2026-12325
ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1
ALT-PU-2026-11249
ALT-PU-2026-11249: package `kernel-image-6.12` update to version 6.12.96-alt1
ALT-PU-2026-11606
ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-64268 In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so the p... | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
CVE-2026-64268 In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so the p... | CVSS3: 8.8 | 1% Низкий | 3 месяца назад | |
CVE-2026-64268 In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so the p | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
CVE-2026-64268 RDMA/siw: bound Read Response placement to the RREAD length | CVSS3: 7.1 | 1% Низкий | 3 месяца назад | |
CVE-2026-64268 In the Linux kernel, the following vulnerability has been resolved: R ... | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
ROS-20261014-80-0201 Уязвимость kernel-lt | CVSS3: 9.8 | 1% Низкий | 12 дней назад | |
ROS-20261014-73-0200 Уязвимость kernel-lt | CVSS3: 9.8 | 1% Низкий | 12 дней назад | |
GHSA-86rp-m36j-7r28 In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: bound Read Response placement to the RREAD length In drivers/infiniband/sw/siw/siw_qp_rx.c, siw_proc_rresp() places each inbound Read Response DDP segment at sge->laddr + wqe->processed and then accumulates wqe->processed, but it never checks the running total against the sink buffer length on continuation segments. siw_check_sge() resolves and validates the sink memory only on the first fragment (the if (!*mem) branch), and siw_rresp_check_ntoh() compares the cumulative length against wqe->bytes only on the final segment (the !frx->more_ddp_segs guard). A connected siw peer that answers an outstanding RREAD with Read Response segments that keep the DDP Last flag clear, carrying more total payload than the RREAD requested, drives wqe->processed past the validated sink buffer; the next siw_rx_data() call writes out of bounds at sge->laddr + wqe->processed. siw runs iWARP over ordinary routable TCP, so th... | CVSS3: 9.8 | 1% Низкий | 3 месяца назад | |
RLSA-2026:63014 Important: kernel security, bug fix, and enhancement update | около 2 месяцев назад | |||
ELSA-2026-63014-0 ELSA-2026-63014-0: kernel security, bug fix, and enhancement update (IMPORTANT) | около 2 месяцев назад | |||
RLSA-2026:63129 Important: kernel security, bug fix, and enhancement update | около 2 месяцев назад | |||
ELSA-2026-63129-0 ELSA-2026-63129-0: kernel security, bug fix, and enhancement update (IMPORTANT) | около 2 месяцев назад | |||
SUSE-SU-2026:4595-1 Security update for the Linux Kernel | 17 дней назад | |||
ALT-PU-2026-11928 ALT-PU-2026-11928: package `kernel-image-std-def` update to version 5.10.262-alt1 | CVSS3: 9.8 | 3 месяца назад | ||
SUSE-SU-2026:4284-1 Security update for the Linux Kernel | около 1 месяца назад | |||
ALT-PU-2026-11926 ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1 | CVSS3: 9.8 | 2 месяца назад | ||
SUSE-SU-2026:4369-1 Security update for the Linux Kernel | 27 дней назад | |||
ALT-PU-2026-12325 ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1 | CVSS3: 9.8 | 3 месяца назад | ||
ALT-PU-2026-11249 ALT-PU-2026-11249: package `kernel-image-6.12` update to version 6.12.96-alt1 | CVSS3: 10 | 3 месяца назад | ||
ALT-PU-2026-11606 ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1 | CVSS3: 10 | 3 месяца назад |
Уязвимостей на страницу