CVE-2026-64268

CVE CVE-2026-64268EUVD EUVD-2026-48980Veröffentlicht 2026-07-25T08:49:16.000ZZuletzt geändert 2026-08-05T12:40:25.000ZCVSS 9.8

Was das Advisory beschreibt

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 untagged paths, and terminate the connection with a base-or-bounds DDP error when the Read Response would overrun the sink buffer. This is the second receive-path length fix for this file. A separate change rejects an MPA FPDU length that underflows the per-fragment remainder in the header decode; that guard does not cover this case, because here each individual segment length is self-consistent and only the accumulated placement offset overruns the buffer.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux patch: 5.15.212; patch: 5.10.261; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <6bc89f34a4597f9f6d41f7a60c67a3153bfe8851; patch: 7.2-rc1; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <b2e26c955f8dd7e8d3f16c858db05245ea4fa817; patch: 6.6.145; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <595e6537ad1a210da32cbb9a7f91aa73090915ba; patch: 7.1.4; patch: 6.1.178; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <3ef7e052cbd05a8b13a51a07b185a39ec93ee1cf; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <a31b6d18ded3cc32d9ee85a6ff0726d4274887b2; 5.3; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <423a78ff7928c2601013f73ec6d896f5597d0df5; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <75c93cd3c421890f49ea93f0b978b9b7bb10e5e3; 8b6a361b8c482f22ac99c3273285ff16b23fba91 <7d29f7e9dbd844cae4d3e559cf78324b9642fd6b; patch: 6.18.39; patch: 6.12.96; patch: 0

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.