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 Cloud Security Plugin ID 466394

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: target: Bound PR-OUT TransportID
parsing to the received buffer core_scsi3_decode_spec_i_port() and core_scsi3_emulate_register_and_move()
hand the raw PERSISTENT RESERVE OUT parameter buffer to target_parse_pr_out_transport_id() without telling
it how many bytes are valid. For an iSCSI TransportID (FORMAT CODE 01b), iscsi_parse_pr_out_transport_id()
locates the ",i,0x" ISID separator with an unbounded strstr() (and on the error path prints the name with
a further unbounded "%s"). An initiator can submit a TransportID whose iSCSI name contains neither a
",i,0x" substring nor a NUL terminator, filling the parameter list to its end, so the scan runs off the
end of the buffer. When the parameter list spans more than one page the buffer is a multi-page vmap
(transport_kmap_data_sg()), so the over-read walks into the trailing vmalloc guard page and oopses (KASAN:
vmalloc-out-of-bounds in strstr). It is reachable by any fabric that delivers a PR OUT to a device
exported through an iSCSI TPG, including a guest via vhost-scsi. Pass the number of received bytes down to
the parser and validate the iSCSI TransportID's own self-described length (ADDITIONAL LENGTH + 4) once, up
front: reject it if it is below the spc4r17 minimum or larger than the received buffer, then bound the
separator search, the ISID walk and the name copy by that length. This is the length check the callers
already perform after the parse (core_scsi3_decode_spec_i_port() compares tid_len against tpdl,
core_scsi3_emulate_register_and_move() validates it against data_length), moved ahead of the scan. Also
drop the unbounded "%s" of the unterminated name. Add per-format explicit name-length checks before
copying into i_str, rather than silently truncating with min_t: for FORMAT CODE 00b reject if the
descriptor body (tid_len - 4 bytes) cannot fit in i_str[TRANSPORT_IQN_LEN]; for FORMAT CODE 01b reject if
the name portion (from &buf[4] up to the separator) cannot fit. Both checks make the bounds intent
explicit at each format branch. While here, also reject a FORMAT CODE 01b TransportID whose ",i,0x"
separator sits at the very end of the descriptor: that leaves an empty ISID and points the returned port
nexus pointer at buf + tid_len, one past the descriptor, which the registration code
(__core_scsi3_locate_pr_reg(), __core_scsi3_alloc_registration()) then dereferences as the ISID string --
the same over-read of the parameter buffer for a malformed descriptor. (CVE-2026-72084)

Solution

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

Plugin Details

Severity: Critical

ID: 466394

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: High

Score: 7.6

Percentile: 98.3

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-72084

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-72084

Detections

Analytics