CVE-2026-64268

Zwakheid

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 peer is the remote end of an established RDMA connection and needs no local privilege. Bound every segment before placement, exactly as siw_proc_send() and siw_proc_write() already do for their tagged and

Getroffen producten

• linux linux_kernel

Bronnen

• https://git.kernel.org/stable/c/3ef7e052cbd05a8b13a51a07b185a39ec93ee1cf
• https://git.kernel.org/stable/c/423a78ff7928c2601013f73ec6d896f5597d0df5
• https://git.kernel.org/stable/c/595e6537ad1a210da32cbb9a7f91aa73090915ba
• https://git.kernel.org/stable/c/6bc89f34a4597f9f6d41f7a60c67a3153bfe8851
• https://git.kernel.org/stable/c/75c93cd3c421890f49ea93f0b978b9b7bb10e5e3
• https://git.kernel.org/stable/c/7d29f7e9dbd844cae4d3e559cf78324b9642fd6b