Detections
Analytics

Google: sys-kernel/cchost-kernel-6_12, sys-kernel/csql-kernel-6_12, sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_12, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_12, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6: security update to 19216.395.138

medium Tenable Self-Hosted Container Security Plugin ID 468682

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: futex: Prevent lockup in requeue-PI
 during signal/ timeout wakeup During wait-requeue-pi (task A) and requeue-PI (task B) the following race
 can happen: Task A Task B futex_wait_requeue_pi() futex_setup_timer() futex_do_wait() futex_requeue()
 CLASS(hb, hb1)(&key1); CLASS(hb, hb2)(&key2); *timeout* futex_requeue_pi_wakeup_sync() requeue_state =
 Q_REQUEUE_PI_IGNORE *blocks on hb->lock* futex_proxy_trylock_atomic() futex_requeue_pi_prepare()
 Q_REQUEUE_PI_IGNORE => -EAGAIN double_unlock_hb(hb1, hb2) *retry* Task B acquires both hb locks and
 attempts to acquire the PI-lock of the top most waiter (task B). Task A is leaving early due to a signal/
 timeout and started removing itself from the queue. It updates its requeue_state but can not remove it
 from the list because this requires the hb lock which is owned by task B. Usually task A is able to swoop
 the lock after task B unlocked it. However if task B is of higher priority then task A may not be able to
 wake up in time and acquire the lock before task B gets it again. Especially on a UP system where A is
 never scheduled. As a result task A blocks on the lock and task B busy loops, trying to make progress but
 live locks the system instead. Tragic. This can be fixed by removing the top most waiter from the list in
 this case. This allows task B to grab the next top waiter (if any) in the next iteration and make
 progress. Remove the top most waiter if futex_requeue_pi_prepare() fails. Let the waiter conditionally
 remove itself from the list in handle_early_requeue_pi_wakeup(). (CVE-2026-52977)

Solution

Update the sys-kernel/cchost-kernel-6_12 library and its related packages to version 19216.395.138 or later.

See Also

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

Plugin Details

Severity: Medium

ID: 468682

Version: Revision 1.5

Type: Local

Published: 10/3/2026

Updated: 10/6/2026

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

Risk Information

VPR

Risk Factor: Medium

Score: 5.7

Percentile: 95.96

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

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: 6/3/2026

Reference Information

CVE: CVE-2026-52977