Поиск уязвимостей
Количество 20
Количество 20
CVE-2026-64269
In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate fi...
CVE-2026-64269
In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate fi...
CVE-2026-64269
In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate
CVE-2026-64269
RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg
CVE-2026-64269
In the Linux kernel, the following vulnerability has been resolved: R ...
ROS-20261014-80-0204
Уязвимость kernel-lt
ROS-20261014-73-0203
Уязвимость kernel-lt
GHSA-ffxc-rc5x-r6rp
In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separ...
BDU:2026-18262
Уязвимость ядра операционной системы Linux, связанная с чтением за допустимыми границами буфера данных, позволяющая нарушителю получить доступ к защищаемой информации, а также вызвать отказ в обслуживании
ALT-PU-2026-11926
ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1
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
ALT-PU-2026-21143
ALT-PU-2026-21143: package `kernel-image-rpi-un` update to version 6.12.115-alt1
ALT-PU-2026-20976
ALT-PU-2026-20976: package `kernel-image-rpi-un` update to version 6.12.115-alt1
SUSE-SU-2026:4254-1
Security update for the Linux Kernel
SUSE-SU-2026:4120-1
Security update for the Linux Kernel
openSUSE-SU-2026:21910-1
Security update for the Linux Kernel
ALT-PU-2026-11671
ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1
openSUSE-SU-2026:22309-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2026-64269 In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate fi... | CVSS3: 9.1 | 1% Низкий | 4 месяца назад | |
CVE-2026-64269 In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate fi... | 1% Низкий | 4 месяца назад | ||
CVE-2026-64269 In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separate | CVSS3: 9.1 | 1% Низкий | 4 месяца назад | |
CVE-2026-64269 RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg | CVSS3: 5.7 | 1% Низкий | 4 месяца назад | |
CVE-2026-64269 In the Linux kernel, the following vulnerability has been resolved: R ... | CVSS3: 9.1 | 1% Низкий | 4 месяца назад | |
ROS-20261014-80-0204 Уязвимость kernel-lt | CVSS3: 9.1 | 1% Низкий | около 1 месяца назад | |
ROS-20261014-73-0203 Уязвимость kernel-lt | CVSS3: 9.1 | 1% Низкий | около 1 месяца назад | |
GHSA-ffxc-rc5x-r6rp In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg When the server answers an RTRS READ, rdma_write_sg() builds the source scatter/gather entry for the IB_WR_RDMA_WRITE that returns data to the peer. Its length is taken directly from the wire descriptor: plist->length = le32_to_cpu(id->rd_msg->desc[0].len); rd_msg points into the chunk buffer that the remote peer filled via RDMA-WRITE-WITH-IMM (rtrs_srv_rdma_done() -> process_io_req() -> process_read()), so desc[0].len is attacker-controlled and, before this change, was only rejected when zero. The source address is the fixed chunk start (dma_addr[msg_id]) and the source lkey is the PD-wide local_dma_lkey, which is not tied to the chunk's MR mapping, so the verbs layer does not constrain the transfer length to max_chunk_size. msg_id and off are bounded against queue_depth and max_chunk_size in rtrs_srv_rdma_done(), but desc[0].len is a separ... | CVSS3: 9.1 | 1% Низкий | 4 месяца назад | |
BDU:2026-18262 Уязвимость ядра операционной системы Linux, связанная с чтением за допустимыми границами буфера данных, позволяющая нарушителю получить доступ к защищаемой информации, а также вызвать отказ в обслуживании | CVSS3: 9.1 | 1% Низкий | 5 месяцев назад | |
ALT-PU-2026-11926 ALT-PU-2026-11926: package `kernel-image-un-def` update to version 6.1.180-alt1 | CVSS3: 9.8 | 3 месяца назад | ||
ALT-PU-2026-12325 ALT-PU-2026-12325: package `kernel-image-for-vm` update to version 6.18.40-alt1 | CVSS3: 9.8 | 4 месяца назад | ||
ALT-PU-2026-11249 ALT-PU-2026-11249: package `kernel-image-6.12` update to version 6.12.96-alt1 | CVSS3: 10 | 4 месяца назад | ||
ALT-PU-2026-11606 ALT-PU-2026-11606: package `kernel-image-6.18` update to version 6.18.40-alt1 | CVSS3: 10 | 4 месяца назад | ||
ALT-PU-2026-21143 ALT-PU-2026-21143: package `kernel-image-rpi-un` update to version 6.12.115-alt1 | CVSS3: 10 | 10 дней назад | ||
ALT-PU-2026-20976 ALT-PU-2026-20976: package `kernel-image-rpi-un` update to version 6.12.115-alt1 | CVSS3: 10 | 13 дней назад | ||
SUSE-SU-2026:4254-1 Security update for the Linux Kernel | 2 месяца назад | |||
SUSE-SU-2026:4120-1 Security update for the Linux Kernel | 2 месяца назад | |||
openSUSE-SU-2026:21910-1 Security update for the Linux Kernel | около 2 месяцев назад | |||
ALT-PU-2026-11671 ALT-PU-2026-11671: package `kernel-image-rt` update to version 6.12.98-alt1 | CVSS3: 10 | 4 месяца назад | ||
openSUSE-SU-2026:22309-1 Security update for the Linux Kernel | 9 дней назад |
Уязвимостей на страницу