IB/isert: reject PDUs declaring more data than was received
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Original description
In the Linux kernel, the following vulnerability has been resolved:
IB/isert: reject PDUs declaring more data than was received
isert_recv_done() hands each received PDU to the opcode handlers without ever looking at wc->byte_len, the number of bytes the HCA actually placed in the receive descriptor. The handlers then copy that many bytes - the data-segment length the initiator declared in the BHS (ntoh24(hdr->dlength), via the derived unsol_data_len / imm_data_len) - out of the fixed-size descriptor:
isert_handle_iscsi_dataout(): sg_copy_from_buffer(sg_start, sg_nents, isert_get_data(rx_desc), unsol_data_len); isert_handle_scsi_cmd(): sg_copy_from_buffer(cmd->se_cmd.t_data_sg, sg_nents, isert_get_data(rx_desc), imm_data_len);
Because the declared length is never checked against wc->byte_len, an initiator can declare a data segment larger than the bytes it actually sent (and larger than the descriptor) and cause an out-of-bounds read of the receive buffer.
Nothing upstream of isert closes this door:
- __iscsit_check_dataout_hdr() bounds the inbound payload against conn_ops->MaxXmitDataSegmentLength (MXDSL) - a transmit parameter, used here for the inbound check. - iscsi_set_connection_parameters() sets ops->MaxXmitDataSegmentLength = ops->TargetRecvDataSegmentLength; and TARGETRECVDATASEGMENTLENGTH is absent from the min()-clamp list in iscsi_check_acceptor_state(), so the value the initiator declares is adopted verbatim (type range 512..16777215). The initiator effectively raises its own ceiling. - isert never clamps the negotiated value to its own fixed receive descriptor (ISER_RX_SIZE, 9216 bytes), so the target core's bound and the descriptor size are unrelated.
The imm_data_len == data_len path is more than an over-read: it aliases the receive descriptor via sg_set_buf() and passes it to the backend as the data source for the SCSI WRITE, so an over-declared length causes heap contents past the descriptor to be written through the backend to the backing store. The backend is the victim of the oversized scatterlist isert hands it, not the cause; no read-back of the written bytes was demonstrated.
From the CVE record · Linux
References
- git.kernel.org/stable/c/b4706722ed3ea72882b3c986a19b4a1ba66384c4
- git.kernel.org/stable/c/bc58e9d3dc560220c57b8bdfc12af0cff1c8a43d
- git.kernel.org/stable/c/274b1ad7e78338710864c4b4235bb1ce7e7107f9
- git.kernel.org/stable/c/2a6b8f88fb7ee51714a1922a039225bdcaf12855
- git.kernel.org/stable/c/39da0b7e1f530347d284cebcfc5b5afa90a173bf
- git.kernel.org/stable/c/cf36fa5357a2fb25776a568d13a3653da7d99bcb
- git.kernel.org/stable/c/352dc85324b29f5c85876f2666f3158b645e3f18
- git.kernel.org/stable/c/957f92ea4022fb6af4618271615a2a21a7b5bef9
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90414.json
- nvd.nist.gov/vuln/detail/CVE-2026-90414
- git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git