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

medium Tenable Cloud Security Plugin ID 466038

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: ext4: always drain queued discard work
in ext4_mb_release() While reviewing recent ext4 patch[1], Sashiko raised the following concern[2]: > If
the filesystem is initially mounted with the discard option, > deleting files will populate
sbi->s_discard_list and queue > s_discard_work. If it is then remounted with nodiscard, the >
EXT4_MOUNT_DISCARD flag is cleared, but the pending s_discard_work is > neither cancelled nor flushed. [1]
https://lore.kernel.org/r/[email protected]/ [2]
https://sashiko.dev/#/patchset/20260319094545.19291-1-qiang.zhang%40linux.dev The concern was valid, but
it had nothing to do with the patch[1]. One of the problems with Sashiko in its current (early) form is
that it will detect pre-existing issues and report it as a problem with the patch that it is reviewing. In
practice, it would be hard to hit deliberately (unless you are a malicious syzkaller fuzzer), since it
would involve mounting the file system with -o discard, and then deleting a large number of files,
remounting the file system with -o nodiscard, and then immediately unmounting the file system before the
queued discard work has a change to drain on its own. Fix it because it's a real bug, and to avoid Sashiko
from raising this concern when analyzing future patches to mballoc.c. (CVE-2026-43065)

Solution

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

Plugin Details

Severity: Medium

ID: 466038

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

Vendor

Vendor Severity: LOW

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

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: 4/23/2026

Reference Information

CVE: CVE-2026-43065

Detections

Analytics