Echo: linux: security update to 6.1.170-1

medium Tenable Cloud Security Plugin ID 459762

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: atm: fix crash due to unvalidated
vcc pointer in sigd_send() Reproducer available at [1]. The ATM send path (sendmsg -> vcc_sendmsg ->
sigd_send) reads the vcc pointer from msg->vcc and uses it directly without any validation. This pointer
comes from userspace via sendmsg() and can be arbitrarily forged: int fd = socket(AF_ATMSVC, SOCK_DGRAM,
0); ioctl(fd, ATMSIGD_CTRL); // become ATM signaling daemon struct msghdr msg = { .msg_iov = &iov, ... };
*(unsigned long *)(buf + 4) = 0xdeadbeef; // fake vcc pointer sendmsg(fd, &msg, 0); // kernel dereferences
0xdeadbeef In normal operation, the kernel sends the vcc pointer to the signaling daemon via sigd_enq()
when processing operations like connect(), bind(), or listen(). The daemon is expected to return the same
pointer when responding. However, a malicious daemon can send arbitrary pointer values. Fix this by
introducing find_get_vcc() which validates the pointer by searching through vcc_hash (similar to how
sigd_close() iterates over all VCCs), and acquires a reference via sock_hold() if found. Since struct
atm_vcc embeds struct sock as its first member, they share the same lifetime. Therefore using
sock_hold/sock_put is sufficient to keep the vcc alive while it is being used. Note that there may be a
race with sigd_close() which could mark the vcc with various flags (e.g., ATM_VF_RELEASED) after
find_get_vcc() returns. However, sock_hold() guarantees the memory remains valid, so this race only
affects the logical state, not memory safety. [1]:
https://gist.github.com/mrpre/1ba5949c45529c511152e2f4c755b0f3 (CVE-2026-31411)

Solution

Update the linux library and its related packages to version 6.1.170-1 or later.

See Also

https://advisory.echohq.com/cve/CVE-2026-31411

Plugin Details

Severity: Medium

ID: 459762

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.71

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

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

Patch Publication Date: 5/1/2026

Vulnerability Publication Date: 3/12/2026

Reference Information

CVE: CVE-2026-31411