Google: sys-kernel/csql-kernel-6_1, sys-kernel/lakitu-kernel-6_1: security update to 18244.85.5

medium Tenable Cloud Security Plugin ID 451640

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: scsi: core: Fix unremoved procfs host
directory regression Commit fc663711b944 ("scsi: core: Remove the /proc/scsi/${proc_name} directory
earlier") fixed a bug related to modules loading/unloading, by adding a call to scsi_proc_hostdir_rm() on
scsi_remove_host(). But that led to a potential duplicate call to the hostdir_rm() routine, since it's
also called from scsi_host_dev_release(). That triggered a regression report, which was then fixed by
commit be03df3d4bfe ("scsi: core: Fix a procfs host directory removal regression"). The fix just dropped
the hostdir_rm() call from dev_release(). But it happens that this proc directory is created on
scsi_host_alloc(), and that function "pairs" with scsi_host_dev_release(), while scsi_remove_host() pairs
with scsi_add_host(). In other words, it seems the reason for removing the proc directory on dev_release()
was meant to cover cases in which a SCSI host structure was allocated, but the call to scsi_add_host()
didn't happen. And that pattern happens to exist in some error paths, for example. Syzkaller causes that
by using USB raw gadget device, error'ing on usb-storage driver, at usb_stor_probe2(). By checking that
path, we can see that the BadDevice label leads to a scsi_host_put() after a SCSI host allocation, but
there's no call to scsi_add_host() in such path. That leads to messages like this in dmesg (and a leak of
the SCSI host proc structure): usb-storage 4-1:87.51: USB Mass Storage device detected proc_dir_entry
'scsi/usb-storage' already registered WARNING: CPU: 1 PID: 3519 at fs/proc/generic.c:377
proc_register+0x347/0x4e0 fs/proc/generic.c:376 The proper fix seems to still call scsi_proc_hostdir_rm()
on dev_release(), but guard that with the state check for SHOST_CREATED; there is even a comment in
scsi_host_dev_release() detailing that: such conditional is meant for cases where the SCSI host was
allocated but there was no calls to {add,remove}_host(), like the usb-storage case. This is what we
propose here and with that, the error path of usb-storage does not trigger the warning anymore.
(CVE-2024-26935)

Solution

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

Plugin Details

Severity: Medium

ID: 451640

Version: Revision 1.2

Type: Local

Family: Google COS Security Checks

Published: 10/1/2026

Updated: 10/2/2026

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

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.18

Vendor

Vendor Severity: MEDIUM

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-2024-26935

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

Reference Information

CVE: CVE-2024-26935

Detections

Analytics