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

medium Tenable Cloud Security Plugin ID 475444

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: tracing/probes: Fix use-after-free on
field name/type of events with multiple probes The fields of a probe-based dynamic event (kprobe, uprobe,
eprobe and fprobe events) are created in traceprobe_define_arg_fields() by handing the probe_arg name/type
strings to trace_define_field(), which only stores the pointers without copying. Those strings are owned
by the trace_probe and are freed when that probe is removed. An event can have several probes attached.
The field list is defined only once, by the first probe that registers the event, but it is kept alive by
any surviving sibling probe. Deleting just that first probe by symbol - # primary A: fields are defined
from A's args echo 'p:kprobes/ev vfs_read a1=$arg1' > kprobe_events # append B: shares A's event call echo
'p:kprobes/ev vfs_write a1=$arg1' >> kprobe_events # delete only A (matched by symbol), B survives echo
'-:kprobes/ev vfs_read' >> kprobe_events frees A's args (trace_probe_cleanup() ->
traceprobe_free_probe_arg()), but trace_probe_unlink() keeps the trace_probe_event because the probe list
is not empty. The event call stays registered via B while its fields now reference freed memory. Any field
lookup then reads it, e.g. echo 'a1 == 1' > events/kprobes/ev/filter BUG: KASAN: slab-use-after-free in
strcmp+0xa7/0xb0 Call Trace: strcmp trace_find_event_field parse_pred process_preds create_filter
apply_event_filter event_filter_write field->name references parg->name (kstrdup'd, freed with the probe)
and, for array arguments, field->type references parg->fmt (kmalloc'd, freed with the probe) - the scalar
type otherwise points at the static fmttype rodata, which is safe. Have traceprobe_define_arg_fields()
duplicate the name and type strings and anchor the copies on the trace_probe_event, which embeds the event
call and outlives every individual probe; trace_probe_event_free() releases them. The reproducer above
triggers reliably; the field lookup and the delete both run under event_mutex, so this is a dangling
reference after removal rather than a race. The issue was found by the autokbug dynamic kernel fuzzer at
Tencent Yunding Lab. (CVE-2026-98076)

Solution

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

Plugin Details

Severity: Medium

ID: 475444

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/16/2026

Updated: 10/16/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.74

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

CVSS v3

Risk Factor: Medium

Base Score: 5.5

Temporal Score: 4.8

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

Reference Information

CVE: CVE-2026-98076

Detections

Analytics