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

high Tenable Self-Hosted Container Security Plugin ID 475207

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: perf/x86/intel/pt: Fix stop/start with
no update If pt_event_stop() is called without PERF_EF_UPDATE flag, then perf_aux_output_end() is not
called. A subsequent call to pt_event_start() will call perf_aux_output_begin() again which violates the
rule against nesting and triggers a WARNING in perf_aux_output_begin(). Originally, pt_event_stop() was
never called without PERF_EF_UPDATE, because the only code paths to do so are from event overflow, and
Intel PT does not do that. However the introduction of group throttling by commit 9734e25fbf5ae ("perf:
Fix the throttle logic for a group") meant that an Intel PT event could be throttled if it was part of a
group. Throttling calls PMU ->stop() / ->start() callbacks without flags. An example is when AUX area
sampling is used. The following commands hit the issue: echo 10000 >
/proc/sys/kernel/perf_event_max_sample_rate perf record -F32000 --aux-sample -e '{intel_pt//u,cycles:u}' \
-- bash -c 'for i in `seq 1 100000` ; do true ; done' Use PERF_HES_UPTODATE to track whether
perf_aux_output_begin() and perf_aux_output_end() are balanced. A cleared PERF_HES_UPTODATE bit indicates
that an AUX output context is still open. Amend pt_event_start() / pt_event_stop() accordingly so that
begin/end stay balanced: - In non-snapshot mode, stop() always closes the buffer (the buffer may have run
out of space, and that accounting is done by the update), so a following start() opens a fresh one as
before. - In snapshot/overwrite mode, stop() without PERF_EF_UPDATE leaves the buffer open so that
pt_event_snapshot_aux() can still copy from it, and start() then only re-enables tracing instead of
calling perf_aux_output_begin() again. Note that pt_event_del() calls pt_event_stop() with PERF_EF_UPDATE
flag set (as is required by the documentation), so a final call to perf_aux_output_end() is assured.
(CVE-2026-93275)

Solution

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

Plugin Details

Severity: High

ID: 475207

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/16/2026

Updated: 10/16/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.3

Percentile: 53.45

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: High

Base Score: 7.2

Temporal Score: 5.3

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

CVSS Score Source: CVE-2026-93275

CVSS v3

Risk Factor: High

Base Score: 7.1

Temporal Score: 6.2

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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: 9/24/2026

Reference Information

CVE: CVE-2026-93275

Detections

Analytics