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

medium Tenable Cloud Security Plugin ID 467104

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: KVM: Don't WARN if memory is dirtied
without a vCPU when the VM is dying When marking a page dirty, complain about not having a running/loaded
vCPU if and only if the VM is still alive, i.e. its refcount is non-zero. This will allow fixing a memory
leak for x86 SEV-ES guests without hitting what is effectively a false positive on the WARN. For some SEV-
ES VM-Exits, KVM keeps a writable mapping of a guest page across an exit to userspace, and typically
unmaps the page on the next KVM_RUN. But if userspace never calls KVM_RUN after such an exit, then KVM
needs to unmap the page when the vCPU is destroyed, which in turn triggers the WARN about not having a
running vCPU. Alternatively, SEV-ES could temporarily load the vCPU to suppress the WARN, as is done in
nested_vmx_free_vcpu() (but for completely unrelated reasons; suppressing WARN from
nested_put_vmcs12_pages() is pure happenstance). But loading a vCPU during destruction is gross (ideally
nVMX code would be cleaned up), risks complicating the SEV-ES code (KVM would need to ensure the
temporarily load()+put() only runs when the vCPU isn't already loaded), and is ultimately pointless. The
motivation for the WARN is to guard against KVM dirtying guest memory without pushing the corresponding
GFN to the active vCPU's dirty ring, e.g. to ensure userspace doesn't miss a dirty page. But for the VM's
refcount to reach zero, there can't be _any_ userspace mappings to the dirty ring, as mapping the dirty
ring requires doing mmap() on the vCPU FD. I.e. if userspace had a valid mapping for the dirty ring, then
the vCPU file and thus the owning VM would still be alive. And so since userspace can't possibly reach the
dirty ring, whether or not KVM technically "misses" a push to the dirty ring is irrelevant.
(CVE-2026-53345)

Solution

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

Plugin Details

Severity: Medium

ID: 467104

Version: Revision 1.3

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/3/2026

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

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.63

Vendor

Vendor Severity: MEDIUM

CVSS v2

Risk Factor: Medium

Base Score: 4.6

Temporal Score: 3.4

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

CVSS Score Source: CVE-2026-53345

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: 7/1/2026

Reference Information

CVE: CVE-2026-53345

Detections

Analytics