Google: sys-kernel/csql-kernel-6_1, sys-kernel/csql-kernel-6_6: security update to 18613.339.70

high Tenable Self-Hosted Container Security Plugin ID 472308

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: eventpoll: don't decrement ep refcount
while still holding the ep mutex Jann Horn points out that epoll is decrementing the ep refcount and then
doing a mutex_unlock(&ep->mtx); afterwards. That's very wrong, because it can lead to a use-after-free.
That pattern is actually fine for the very last reference, because the code in question will delay the
actual call to "ep_free(ep)" until after it has unlocked the mutex. But it's wrong for the much subtler
"next to last" case when somebody *else* may also be dropping their reference and free the ep while we're
still using the mutex. Note that this is true even if that other user is also using the same ep mutex:
mutexes, unlike spinlocks, can not be used for object ownership, even if they guarantee mutual exclusion.
A mutex "unlock" operation is not atomic, and as one user is still accessing the mutex as part of
unlocking it, another user can come in and get the now released mutex and free the data structure while
the first user is still cleaning up. See our mutex documentation in Documentation/locking/mutex-
design.rst, in particular the section [1] about semantics: "mutex_unlock() may access the mutex structure
even after it has internally released the lock already - so it's not safe for another context to acquire
the mutex and assume that the mutex_unlock() context is not using the structure anymore" So if we drop our
ep ref before the mutex unlock, but we weren't the last one, we may then unlock the mutex, another user
comes in, drops _their_ reference and releases the 'ep' as it now has no users - all while the
mutex_unlock() is still accessing it. Fix this by simply moving the ep refcount dropping to outside the
mutex: the refcount itself is atomic, and doesn't need mutex protection (that's the whole _point_ of
refcounts: unlike mutexes, they are inherently about object lifetimes). (CVE-2025-38349)

Solution

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

Plugin Details

Severity: High

ID: 472308

Version: Revision 1.2

Type: Local

Family: Google COS Security Checks

Published: 10/3/2026

Updated: 10/5/2026

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

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 57.27

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-2025-38349

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

Reference Information

CVE: CVE-2025-38349

Detections

Analytics