Detections
Analytics

Google: sys-kernel/csql-kernel-6_1, sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_1, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6, sys-kernel/tpusev-kernel-6_6: security update to 18613.731.2

critical Tenable Self-Hosted Container Security Plugin ID 466139

Description

There are packages installed that are affected by a vulnerability referenced in the following CVE:

 - 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. (CVE-2026-74556)

Solution

Update the sys-kernel/csql-kernel-6_1 library and its related packages to version 18613.731.2 or later.

See Also

https://storage.googleapis.com/cos-oval-vulnerability-feed/cos-117.oval.xml.tar.gz

Plugin Details

Severity: Critical

ID: 466139

Version: Revision 1.2

Type: Local

Published: 10/2/2026

Updated: 10/3/2026

Risk Information

VPR

Risk Factor: Medium

Score: 6.9

Percentile: 96.56

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Critical

Base Score: 10

Temporal Score: 7.4

Vector: CVSS2#AV:N/AC:L/Au:N/C:C/I:C/A:C

CVSS Score Source: CVE-2026-74556

CVSS v3

Risk Factor: Critical

Base Score: 9.8

Temporal Score: 8.5

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

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

Exploit Ease: No known exploits are available

Vulnerability Publication Date: 8/11/2026

Reference Information

CVE: CVE-2026-74556