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

high Tenable Self-Hosted Container Security Plugin ID 469944

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: Fix use-after-free in
trace_pipe read on sub-buffer order change Writing to buffer_subbuf_size_kb calls
ring_buffer_subbuf_order_set(), which frees every sub-buffer of the ring buffer, including the reader
page, and replaces them with newly allocated ones. Readers of trace_pipe hold pointers into those pages.
ring_buffer_peek() looks up an event under cpu_buffer->reader_lock but returns the event pointer after
dropping the lock, and peek_next_entry() then calls ring_buffer_event_length() and
ring_buffer_event_data() on it. If the sub-buffer order is changed in that window, the reader dereferences
freed memory: BUG: KASAN: use-after-free in ring_buffer_peek+0x3e0/0x430 Read of size 1 at addr
ffff88802a4cf010 by task syz-executor989/6002 Freed by: free_buffer_page kernel/trace/ring_buffer.c:398
[inline] ring_buffer_subbuf_order_set+0x1325/0x18e0 kernel/trace/ring_buffer.c:7444
buffer_subbuf_size_write+0x182/0x280 kernel/trace/trace.c:8221 Take
trace_access_lock(RING_BUFFER_ALL_CPUS) around the order change. This is the lock trace_pipe readers
already hold across their entire peek-and-print loop, so the swap can no longer race with a reader that is
dereferencing a peeked event. (CVE-2026-89747)

Solution

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

Plugin Details

Severity: High

ID: 469944

Version: Revision 1.3

Type: Local

Family: Google COS Security Checks

Published: 10/3/2026

Updated: 10/3/2026

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

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 58.22

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5

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

CVSS Score Source: CVE-2026-89747

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.8

Vector: CVSS:3.0/AV:L/AC:L/PR:L/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: 9/11/2026

Reference Information

CVE: CVE-2026-89747

Detections

Analytics