CVE-2026-74556

CVE CVE-2026-74556EUVD EUVD-2026-59621Published 2026-08-15T12:28:01.000ZLast changed 2026-08-19T16:38:57.000ZCVSS 9.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux a081c13e39b5c17052a7b46fafa61019c4c110ff <c97b5265cc47775f77fd2a23d6bde0426997b233; patch: 7.2; a081c13e39b5c17052a7b46fafa61019c4c110ff <72815741715bd41556dac5eeb068bf0f8af06ee7; patch: 7.1.8; patch: 5.10.265; a081c13e39b5c17052a7b46fafa61019c4c110ff <a51812842084fd390590ab8dc0431f10c73ddc56; a081c13e39b5c17052a7b46fafa61019c4c110ff <a8f94cc9f0e5759252551be3a172960c57f21f54; patch: 6.12.103; patch: 0; a081c13e39b5c17052a7b46fafa61019c4c110ff <b0aa3e8e2ab4ca92adb28a3ef41873b3363b8676; patch: 6.18.44; a081c13e39b5c17052a7b46fafa61019c4c110ff <084af0253673425ce2ae62e3c7f74f0dd023711b; patch: 6.6.151; a081c13e39b5c17052a7b46fafa61019c4c110ff <f1a3a51fc5dba0e99532379665069f1700da6b44; 2.6.29; a081c13e39b5c17052a7b46fafa61019c4c110ff <c1dea15f819cded9b3faf58f8bec72323568b6e6; patch: 6.1.183; patch: 5.15.216

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.