Google: sys-kernel/csql-kernel-6_6, 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.731.2

medium Tenable Cloud Security Plugin ID 467096

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: net/sched: sch_hfsc: Don't make class
passive twice update_vf() is called from two places for the same class during a single dequeue when the
class's child qdisc (e.g. codel/fq_codel) drops its last packets while dequeuing: 1. The child calls
qdisc_tree_reduce_backlog(), which, now that the child is empty, invokes hfsc_qlen_notify() ->
update_vf(cl, 0, 0) and turns the class passive (cl_nactive is decremented up the hierarchy). 2.
hfsc_dequeue() then calls update_vf(cl, qdisc_pkt_len(skb), cur_time) to charge the dequeued bytes. On the
second call the class is already passive, but its child qdisc is still empty, so update_vf() arms
go_passive again: if (cl->qdisc->q.qlen == 0 && cl->cl_flags & HFSC_FSC) go_passive = 1; The leaf is then
skipped by the cl_nactive == 0 check inside the loop, which does not clear go_passive, so the stale
go_passive propagates to the parent and decrements its cl_nactive a second time. A parent that still has
other active children is driven to cl_nactive == 0 and removed from the vttree, even though those siblings
are still backlogged. They are never dequeued again and the qdisc stalls. Fix this by only arming
go_passive when the class is actually active, so an already-passive class no longer triggers a second
passive transition. The byte accounting (cl->cl_total += len) still runs for every ancestor, so dequeued
bytes continue to be counted exactly once. (CVE-2026-74284)

Solution

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

Plugin Details

Severity: Medium

ID: 467096

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.59

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-2026-74284

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: 8/11/2026

Reference Information

CVE: CVE-2026-74284

Detections

Analytics