Answer in brief
CVE-2026-74556 records a Unknown severity vulnerability in scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a081c13e39b5c17052a7b46fafa61019c4c110ff <c97b5265cc47775f77fd2a23d6bde0426997b233 || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <084af0253673425ce2ae62e3c7f74f0dd023711b || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <72815741715bd41556dac5eeb068bf0f8af06ee7 || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <b0aa3e8e2ab4ca92adb28a3ef41873b3363b8676 || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <c1dea15f819cded9b3faf58f8bec72323568b6e6 | c97b5265cc47775f77fd2a23d6bde0426997b233, 084af0253673425ce2ae62e3c7f74f0dd023711b, 72815741715bd41556dac5eeb068bf0f8af06ee7, b0aa3e8e2ab4ca92adb28a3ef41873b3363b8676, c1dea15f819cded9b3faf58f8bec72323568b6e6 |
| Linux/Linuxgeneric | 2.6.29 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74556 records a Unknown severity vulnerability in scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a081c13e39b5c17052a7b46fafa61019c4c110ff <c97b5265cc47775f77fd2a23d6bde0426997b233 || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <084af0253673425ce2ae62e3c7f74f0dd023711b || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <72815741715bd41556dac5eeb068bf0f8af06ee7 || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <b0aa3e8e2ab4ca92adb28a3ef41873b3363b8676 || >=a081c13e39b5c17052a7b46fafa61019c4c110ff <c1dea15f819cded9b3faf58f8bec72323568b6e6 | c97b5265cc47775f77fd2a23d6bde0426997b233, 084af0253673425ce2ae62e3c7f74f0dd023711b, 72815741715bd41556dac5eeb068bf0f8af06ee7, b0aa3e8e2ab4ca92adb28a3ef41873b3363b8676, c1dea15f819cded9b3faf58f8bec72323568b6e6 |
| Linux/Linuxgeneric | 2.6.29 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.