Google: sys-kernel/csql-kernel-6_1, sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_1, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6, sys-kernel/tpusev-kernel-6_6: security update to 18613.613.15

high Tenable Self-Hosted Container Security Plugin ID 466043

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: ptrace: slightly saner
'get_dumpable()' logic The 'dumpability' of a task is fundamentally about the memory image of the task -
the concept comes from whether it can core dump or not - and makes no sense when you don't have an
associated mm. And almost all users do in fact use it only for the case where the task has a mm pointer.
But we have one odd special case: ptrace_may_access() uses 'dumpable' to check various other things
entirely independently of the MM (typically explicitly using flags like PTRACE_MODE_READ_FSCREDS).
Including for threads that no longer have a VM (and maybe never did, like most kernel threads). It's not
what this flag was designed for, but it is what it is. The ptrace code does check that the uid/gid
matches, so you do have to be uid-0 to see kernel thread details, but this means that the traditional
"drop capabilities" model doesn't make any difference for this all. Make it all make a *bit* more sense by
saying that if you don't have a MM pointer, we'll use a cached "last dumpability" flag if the thread ever
had a MM (it will be zero for kernel threads since it is never set), and require a proper CAP_SYS_PTRACE
capability to override. (CVE-2026-46333)

Solution

Update the sys-kernel/csql-kernel-6_1 library and its related packages to version 18613.613.15 or later.

Plugin Details

Severity: High

ID: 466043

Version: Revision 1.2

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/3/2026

Risk Information

VPR

Risk Factor: High

Score: 8.9

Percentile: 99.71

Vendor

Vendor Severity: HIGH

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5.3

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

CVSS Score Source: CVE-2026-46333

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 7

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:P/RL:O/RC:C

Vulnerability Information

Exploit Available: true

Exploit Ease: Exploits are available

Vulnerability Publication Date: 5/15/2026

Reference Information

CVE: CVE-2026-46333

Detections

Analytics