Google: sys-kernel/lakitu-kernel-6_1: security update to 18244.236.77

high Tenable Cloud Security Plugin ID 451571

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: explicitly clear the sk pointer,
when pf->create fails We have recently noticed the exact same KASAN splat as in commit 6cd4a78d962b ("net:
do not leave a dangling sk pointer, when socket creation fails"). The problem is that commit did not fully
address the problem, as some pf->create implementations do not use sk_common_release in their error paths.
For example, we can use the same reproducer as in the above commit, but changing ping to arping. arping
uses AF_PACKET socket and if packet_create fails, it will just sk_free the allocated sk object. While we
could chase all the pf->create implementations and make sure they NULL the freed sk object on error from
the socket, we can't guarantee future protocols will not make the same mistake. So it is easier to just
explicitly NULL the sk pointer upon return from pf->create in __sock_create. We do know that pf->create
always releases the allocated sk object on error, so if the pointer is not NULL, it is definitely
dangling. (CVE-2024-50186)

Solution

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

Plugin Details

Severity: High

ID: 451571

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

Percentile: 57.15

Vendor

Vendor Severity: HIGH

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5

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

CVSS Score Source: CVE-2024-50186

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.8

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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: 10/31/2024

Reference Information

CVE: CVE-2024-50186

Detections

Analytics