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

medium Tenable Cloud Security Plugin ID 467095

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: kcov: fix data corruption and race
conditions on PREEMPT_RT syzbot is reporting KCOV state corruption on PREEMPT_RT kernels, for the
temporary storage used for saving/restoring remote KCOV state is currently allocated as the per-CPU area.
On PREEMPT_RT kernels, softirq handlers run as preemptible task threads (e.g., ksoftirqd). If a softirq
context preempts a task running a remote KCOV session, it safely saves the task's state into the per-CPU
area. However, if that softirq thread is subsequently preempted by a higher- priority softirq thread on
the same CPU, the second softirq will overwrite the same per-CPU area, permanently destroying the original
task's KCOV state. Fix this data corruption by moving the temporary storage from the per-CPU area to the
per-thread area. Since each softirq thread now owns its own task context, nested softirq preemption no
longer causes data overwrites. Note that while the temporary storage is now on a per-thread basis, the
per-CPU kcov_percpu_data.lock must be retained, for we need to ensure that kcov_remote_start() and
kcov_remote_stop() operate atomically without racing against asynchronous interrupts that manipulate the
current task's KCOV state. It is likely that GFP_KERNEL allocation by vmalloc_node() in kcov_init() has
already called panic() before returning NULL, for there will be no OOM-killable userspace processes when
__init function of built-in module runs. But this patch also fixes crashing the kernel when vmalloc_node()
in kcov_init() returned NULL, for kcov_init() left per-CPU irq_area == NULL but kcov_remote_start()
depends on per-CPU irq_area != NULL, resulting in (1) doing vmalloc() in kcov_remote_start() despite
!in_task() context (2) out-of-array-bounds access if (1) succeeded but kcov->remote_size <
CONFIG_KCOV_IRQ_AREA_SIZE (3) always leak memory allocated by (1), eventually killing all OOM-killable
userspace processes problems. (CVE-2026-80916)

Solution

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

Plugin Details

Severity: Medium

ID: 467095

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.59

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Medium

Base Score: 4

Temporal Score: 3

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

CVSS Score Source: CVE-2026-80916

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/9/2026

Reference Information

CVE: CVE-2026-80916

Detections

Analytics