Google: sys-kernel/cchost-kernel-6_12, sys-kernel/csql-kernel-6_12, sys-kernel/lakitu-kernel-6_12, sys-kernel/lakitu-nc-kernel-6_12: security update to 19506.299.3

critical Tenable Cloud Security Plugin ID 469480

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: block: recompute nr_integrity_segments
in blk_insert_cloned_request blk_insert_cloned_request() already recomputes nr_phys_segments against the
bottom queue, because "the queue settings related to segment counting may differ from the original queue."
The exact same reasoning applies to integrity segments: a stacked driver's underlying queue can have
tighter virt_boundary_mask, seg_boundary_mask, or max_segment_size than the top queue, in which case
blk_rq_count_integrity_sg() against the bottom queue produces a different count than the cached
rq->nr_integrity_segments inherited from the source request by blk_rq_prep_clone(). When the cached count
is lower than the bottom queue's actual count, blk_rq_map_integrity_sg() trips BUG_ON(segments >
rq->nr_integrity_segments); on dispatch. The same families of stacked setups that motivated the existing
nr_phys_segments recompute -- dm-multipath fanning out to nvme-rdma in particular -- can produce this.
Mirror the nr_phys_segments handling: when the request carries integrity, recompute nr_integrity_segments
against the bottom queue and reject the request if it exceeds the bottom queue's max_integrity_segments.
blk_rq_count_integrity_sg() and queue_max_integrity_segments() are both already available via <linux/blk-
integrity.h>, which blk-mq.c includes. This closes a latent gap in the stacking contract and brings the
integrity-segment accounting in line with the existing phys-segment accounting. (CVE-2026-64232)

Solution

Update the sys-kernel/cchost-kernel-6_12 library and its related packages to version 19506.299.3 or later.

Plugin Details

Severity: Critical

ID: 469480

Version: Revision 1.6

Type: Local

Family: Google COS Security Checks

Published: 10/3/2026

Updated: 10/6/2026

Supported Sensors: Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: Medium

Score: 6.9

Percentile: 96.84

Vendor

Vendor Severity: HIGH

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

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: 6/4/2026

Reference Information

CVE: CVE-2026-64232

Detections

Analytics