CVE-2026-74556
Linux kernel vulnerability
- Published15 Aug 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://git.kernel.org/stable/c/084af0253673425ce2ae62e3c7f74f0dd023711b
- https://git.kernel.org/stable/c/72815741715bd41556dac5eeb068bf0f8af06ee7
- https://git.kernel.org/stable/c/a51812842084fd390590ab8dc0431f10c73ddc56
- https://git.kernel.org/stable/c/a8f94cc9f0e5759252551be3a172960c57f21f54
- https://git.kernel.org/stable/c/b0aa3e8e2ab4ca92adb28a3ef41873b3363b8676
- https://git.kernel.org/stable/c/c1dea15f819cded9b3faf58f8bec72323568b6e6
- https://git.kernel.org/stable/c/c97b5265cc47775f77fd2a23d6bde0426997b233
- https://git.kernel.org/stable/c/f1a3a51fc5dba0e99532379665069f1700da6b44
Frequently asked
Is CVE-2026-74556 being actively exploited?
CVE-2026-74556 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.40%.
How severe is CVE-2026-74556?
CVE-2026-74556 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.40% probability of exploitation.
How do I fix CVE-2026-74556?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-74556 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.