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

high Tenable Cloud Security Plugin ID 467173

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: fscrypt: Avoid dynamic allocation in
fscrypt_get_devices() When a blk_crypto_key starts being used or is evicted, fs/crypto/ calls
fscrypt_get_devices() to get the filesystem's list of block devices, then iterates over them and calls
blk_crypto_config_supported(), blk_crypto_start_using_key(), or blk_crypto_evict_key() on each one.
Currently, the block device pointers are placed in a dynamically allocated array. This dynamic allocation
is problematic because: - It can fail, especially at the fscrypt_destroy_inline_crypt_key() call site when
it's invoked for inode eviction under direct reclaim. - fscrypt_destroy_inline_crypt_key() doesn't handle
the failure. It just zeroizes and frees the blk_crypto_key without calling blk_crypto_evict_key(). That
causes a use-after-free. For now, let's fix this in the straightforward and easily-backportable way by
switching to an on-stack array. Currently the fscrypt multi-device functionality is used only by f2fs,
which has a hardcoded limit of 8 block devices. An on-stack array works fine for that. (Of course, this
solution won't scale up to large number of block devices. For that we'd need a different solution, like
moving the block device iteration into the filesystem. Or in the case of btrfs, which will only support
blk-crypto-fallback, we should make it just call blk-crypto-fallback directly, so the block devices won't
be needed.) (CVE-2026-68147)

Solution

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

Plugin Details

Severity: High

ID: 467173

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 58.15

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

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: 8/10/2026

Reference Information

CVE: CVE-2026-68147

Detections

Analytics