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

medium Tenable Self-Hosted Container Security Plugin ID 451641

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: PCI/PM: Drain runtime-idle callbacks
before driver removal A race condition between the .runtime_idle() callback and the .remove() callback in
the rtsx_pcr PCI driver leads to a kernel crash due to an unhandled page fault [1]. The problem is that
rtsx_pci_runtime_idle() is not expected to be running after pm_runtime_get_sync() has been called, but the
latter doesn't really guarantee that. It only guarantees that the suspend and resume callbacks will not be
running when it returns. However, if a .runtime_idle() callback is already running when
pm_runtime_get_sync() is called, the latter will notice that the runtime PM status of the device is
RPM_ACTIVE and it will return right away without waiting for the former to complete. In fact, it cannot
wait for .runtime_idle() to complete because it may be called from that callback (it arguably does not
make much sense to do that, but it is not strictly prohibited). Thus in general, whoever is providing a
.runtime_idle() callback needs to protect it from running in parallel with whatever code runs after
pm_runtime_get_sync(). [Note that .runtime_idle() will not start after pm_runtime_get_sync() has returned,
but it may continue running then if it has started earlier.] One way to address that race condition is to
call pm_runtime_barrier() after pm_runtime_get_sync() (not before it, because a nonzero value of the
runtime PM usage counter is necessary to prevent runtime PM callbacks from being invoked) to wait for the
.runtime_idle() callback to complete should it be running at that point. A suitable place for doing that
is in pci_device_remove() which calls pm_runtime_get_sync() before removing the driver, so it may as well
call pm_runtime_barrier() subsequently, which will prevent the race in question from occurring, not just
in the rtsx_pcr driver, but in any PCI drivers providing .runtime_idle() callbacks. (CVE-2024-35809)

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: 451641

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/1/2026

Updated: 10/1/2026

Risk Information

VPR

Risk Factor: Medium

Score: 5

Percentile: 93.13

Vendor

Vendor Severity: MEDIUM

CVSS v2

Risk Factor: Low

Base Score: 3.8

Temporal Score: 2.8

Vector: CVSS2#AV:L/AC:H/Au:S/C:N/I:N/A:C

CVSS Score Source: CVE-2024-35809

CVSS v3

Risk Factor: Medium

Base Score: 4.7

Temporal Score: 4.1

Vector: CVSS:3.0/AV:L/AC:H/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: 12/12/2023

Reference Information

CVE: CVE-2024-35809

Detections

Analytics