Google: sys-kernel/lakitu-kernel-6_1, sys-kernel/lakitu-kernel-6_6: security update to 18514.0.0

medium Tenable Self-Hosted Container Security Plugin ID 473435

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: md/raid5: fix deadlock that raid5d()
wait for itself to clear MD_SB_CHANGE_PENDING Xiao reported that lvm2 test lvconvert-raid-takeover.sh can
hang with small possibility, the root cause is exactly the same as commit bed9e27baf52 ("Revert "md/raid5:
Wait for MD_SB_CHANGE_PENDING in raid5d"") However, Dan reported another hang after that, and junxiao
investigated the problem and found out that this is caused by plugged bio can't issue from raid5d().
Current implementation in raid5d() has a weird dependence: 1) md_check_recovery() from raid5d() must hold
'reconfig_mutex' to clear MD_SB_CHANGE_PENDING; 2) raid5d() handles IO in a deadloop, until all IO are
issued; 3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared; This behaviour is introduce
before v2.6, and for consequence, if other context hold 'reconfig_mutex', and md_check_recovery() can't
update super_block, then raid5d() will waste one cpu 100% by the deadloop, until 'reconfig_mutex' is
released. Refer to the implementation from raid1 and raid10, fix this problem by skipping issue IO if
MD_SB_CHANGE_PENDING is still set after md_check_recovery(), daemon thread will be woken up when
'reconfig_mutex' is released. Meanwhile, the hang problem will be fixed as well. (CVE-2024-39476)

Solution

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

Plugin Details

Severity: Medium

ID: 473435

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/6/2026

Updated: 10/6/2026

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-39476

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/26/2024

Reference Information

CVE: CVE-2024-39476

Detections

Analytics