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.120.97

critical Tenable Cloud Security Plugin ID 470398

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: ext4: handle wraparound when searching
for blocks for indirect mapped blocks Commit 4865c768b563 ("ext4: always allocate blocks only from groups
inode can use") restricts what blocks will be allocated for indirect block based files to block numbers
that fit within 32-bit block numbers. However, when using a review bot running on the latest Gemini LLM to
check this commit when backporting into an LTS based kernel, it raised this concern: If
ac->ac_g_ex.fe_group is >= ngroups (for instance, if the goal group was populated via stream allocation
from s_mb_last_groups), then start will be >= ngroups. Does this allow allocating blocks beyond the 32-bit
limit for indirect block mapped files? The commit message mentions that ext4_mb_scan_groups_linear() takes
care to not select unsupported groups. However, its loop uses group = *start, and the very first iteration
will call ext4_mb_scan_group() with this unsupported group because next_linear_group() is only called at
the end of the iteration. After reviewing the code paths involved and considering the LLM review, I
determined that this can happen when there is a file system where some files/directories are extent-mapped
and others are indirect-block mapped. To address this, add a safety clamp in ext4_mb_scan_groups().
(CVE-2026-43067)

Solution

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

Plugin Details

Severity: Critical

ID: 470398

Version: Revision 1.5

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: 4.9

Percentile: 57.87

Vendor

Vendor Severity: CRITICAL

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

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

Reference Information

CVE: CVE-2026-43067

Detections

Analytics