KernelScan.io

CRITICAL Introduced in 2.6.29

libiscsi_tcp CmdRsp Overflow

CVE-2026-74556

CVSS 9.8 / 10.0 NVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

KernelScan AI9.8CRITICAL

01

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer iscsi_tcp_hdr_dissect() receives the data segment of several PDU types into the fixed-size conn->data buffer, which is allocated for ISCSI_DEF_MAX_RECV_SEG_LEN (8192) bytes. For the LOGIN_RSP, TEXT_RSP, REJECT and ASYNC_EVENT opcodes the dissect path already rejects a PDU whose DataSegmentLength exceeds that buffer. The SCSI Command Response (ISCSI_OP_SCSI_CMD_RSP) path also copies its data segment (sense/response data) into conn->data via iscsi_tcp_data_recv_prep(), but it does so without the same check. The only upstream bound on in.datalen is conn->max_recv_dlength, the initiator's advertised MaxRecvDataSegmentLength, which is commonly negotiated well above 8192 (open-iscsi defaults to 262144). A target that returns a SCSI Response with a DataSegmentLength between 8193 and max_recv_dlength therefore overflows the 8192-byte conn->data buffer. Once the same bound applies, ISCSI_OP_SCSI_CMD_RSP is handled exactly like those responses: bound the data segment, receive it into conn->data when present, and otherwise complete the PDU with no data. Fold the opcode into that case group rather than duplicating the check.

02

Engine v0.6.0

Risk summary

A malicious or compromised iSCSI target can overflow a fixed 8192-byte kernel buffer on any initiator that connects to it, by sending a SCSI Response PDU whose data segment exceeds the buffer but stays within the negotiated maximum. This yields remote kernel memory corruption with no privileges required on the victim. Any system acting as an iSCSI initiator and connecting to an untrusted or compromised target is at critical risk.

Affecteddrivers/scsi/libiscsi_tcp.c (iSCSI TCP transport library)

Vulnerability analysis

When an iSCSI initiator receives a SCSI Command Response from a target, it copies the response's data segment (sense or response data) into a fixed-size connection buffer without first checking that the segment length fits. Other response types already enforce this bound, but the SCSI Response path omits it, relying only on the negotiated maximum receive length—which is commonly set far above the 8192-byte buffer. A malicious or compromised iSCSI target can therefore send a SCSI Response with an oversized data segment, overflowing the buffer and corrupting adjacent kernel memory. The fix applies the same length validation to SCSI Responses that other responses already use, rejecting any oversized data segment before it reaches the buffer. Any system acting as an iSCSI initiator is exposed whenever it connects to an untrusted or compromised target, or when an attacker can intercept the iSCSI TCP connection.

03

BranchIntroducedFixed inPatch commit
6.122.6.296.12.103084af0253673
5.102.6.295.10.265a51812842084
5.152.6.295.15.216a8f94cc9f0e5
6.182.6.296.18.4472815741715b
7.12.6.297.1.8b0aa3e8e2ab4
mainline2.6.297.2c1dea15f819c
6.62.6.296.6.151c97b5265cc47
6.12.6.296.1.183f1a3a51fc5db