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

high Tenable Self-Hosted Container Security Plugin ID 466452

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: fix dirtyclusters double
decrement on fs shutdown fstests test generic/388 occasionally reproduces a warning in ext4_put_super()
associated with the dirty clusters count: WARNING: CPU: 7 PID: 76064 at fs/ext4/super.c:1324
ext4_put_super+0x48c/0x590 [ext4] Tracing the failure shows that the warning fires due to an
s_dirtyclusters_counter value of -1. IOW, this appears to be a spurious decrement as opposed to some sort
of leak. Further tracing of the dirty cluster count deltas and an LLM scan of the resulting output
identified the cause as a double decrement in the error path between ext4_mb_mark_diskspace_used() and the
caller ext4_mb_new_blocks(). First, note that generic/388 is a shutdown vs. fsstress test and so produces
a random set of operations and shutdown injections. In the problematic case, the shutdown triggers an
error return from the ext4_handle_dirty_metadata() call(s) made from ext4_mb_mark_context(). The changed
value is non-zero at this point, so ext4_mb_mark_diskspace_used() does not exit after the error bubbles up
from ext4_mb_mark_context(). Instead, the former decrements both cluster counters and returns the error up
to ext4_mb_new_blocks(). The latter falls into the !ar->len out path which decrements the dirty clusters
counter a second time, creating the inconsistency. To avoid this problem and simplify ownership of the
cluster reservation in this codepath, lift the counter reduction to a single place in the caller. This
makes it more clear that ext4_mb_new_blocks() is responsible for acquiring cluster reservation (via
ext4_claim_free_clusters()) in the !delalloc case as well as releasing it, regardless of whether it ends
up consumed or returned due to failure. (CVE-2026-45920)

Solution

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

See Also

https://storage.googleapis.com/cos-oval-vulnerability-feed/cos-117.oval.xml.tar.gz

Plugin Details

Severity: High

ID: 466452

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 58.14

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

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: 3/27/2026

Reference Information

CVE: CVE-2026-45920