Detections
Analytics

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

medium Tenable Cloud Security Plugin ID 466233

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: fs: Prevent file descriptor table
 allocations exceeding INT_MAX When sysctl_nr_open is set to a very high value (for example, 1073741816 as
 set by systemd), processes attempting to use file descriptors near the limit can trigger massive memory
 allocation attempts that exceed INT_MAX, resulting in a WARNING in mm/slub.c: WARNING: CPU: 0 PID: 44 at
 mm/slub.c:5027 __kvmalloc_node_noprof+0x21a/0x288 This happens because kvmalloc_array() and kvmalloc()
 check if the requested size exceeds INT_MAX and emit a warning when the allocation is not flagged with
 __GFP_NOWARN. Specifically, when nr_open is set to 1073741816 (0x3ffffff8) and a process calls dup2(oldfd,
 1073741880), the kernel attempts to allocate: - File descriptor array: 1073741880 * 8 bytes =
 8,589,935,040 bytes - Multiple bitmaps: ~400MB - Total allocation size: > 8GB (exceeding INT_MAX =
 2,147,483,647) Reproducer: 1. Set /proc/sys/fs/nr_open to 1073741816: # echo 1073741816 >
 /proc/sys/fs/nr_open 2. Run a program that uses a high file descriptor: #include <unistd.h> #include
 <sys/resource.h> int main() { struct rlimit rlim = {1073741824, 1073741824}; setrlimit(RLIMIT_NOFILE,
 &rlim); dup2(2, 1073741880); // Triggers the warning return 0; } 3. Observe WARNING in dmesg at
 mm/slub.c:5027 systemd commit a8b627a introduced automatic bumping of fs.nr_open to the maximum possible
 value. The rationale was that systems with memory control groups (memcg) no longer need separate file
 descriptor limits since memory is properly accounted. However, this change overlooked that: 1. The
 kernel's allocation functions still enforce INT_MAX as a maximum size regardless of memcg accounting 2.
 Programs and tests that legitimately test file descriptor limits can inadvertently trigger massive
 allocations 3. The resulting allocations (>8GB) are impractical and will always fail systemd's algorithm
 starts with INT_MAX and keeps halving the value until the kernel accepts it. On most systems, this results
 in nr_open being set to 1073741816 (0x3ffffff8), which is just under 1GB of file descriptors. While
 processes rarely use file descriptors near this limit in normal operation, certain selftests (like
 tools/testing/selftests/core/unshare_test.c) and programs that test file descriptor limits can trigger
 this issue. Fix this by adding a check in alloc_fdtable() to ensure the requested allocation size does not
 exceed INT_MAX. This causes the operation to fail with -EMFILE instead of triggering a kernel warning and
 avoids the impractical >8GB memory allocation request. (CVE-2025-39756)

Solution

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

See Also

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

Plugin Details

Severity: Medium

ID: 466233

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Medium

Score: 5.7

Percentile: 96.82

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

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: 9/4/2025

Reference Information

CVE: CVE-2025-39756