Detections
Analytics

Echo: linux: security update to 6.12.69-1

medium Tenable Cloud Security Plugin ID 461166

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: netfilter: nf_tables: avoid chain re-
 validation if possible Hamza Mahfooz reports cpu soft lock-ups in nft_chain_validate(): watchdog: BUG:
 soft lockup - CPU#1 stuck for 27s! [iptables-nft-re:37547] [..] RIP: 0010:nft_chain_validate+0xcb/0x110
 [nf_tables] [..] nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables]
 nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables]
 nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables]
 nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables]
 nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables]
 nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables]
 nft_table_validate+0x6b/0xb0 [nf_tables] nf_tables_validate+0x8b/0xa0 [nf_tables]
 nf_tables_commit+0x1df/0x1eb0 [nf_tables] [..] Currently nf_tables will traverse the entire table (chain
 graph), starting from the entry points (base chains), exploring all possible paths (chain jumps). But
 there are cases where we could avoid revalidation. Consider: 1 input -> j2 -> j3 2 input -> j2 -> j3 3
 input -> j1 -> j2 -> j3 Then the second rule does not need to revalidate j2, and, by extension j3, because
 this was already checked during validation of the first rule. We need to validate it only for rule 3. This
 is needed because chain loop detection also ensures we do not exceed the jump stack: Just because we know
 that j2 is cycle free, its last jump might now exceed the allowed stack size. We also need to update all
 reachable chains with the new largest observed call depth. Care has to be taken to revalidate even if the
 chain depth won't be an issue: chain validation also ensures that expressions are not called from invalid
 base chains. For example, the masquerade expression can only be called from NAT postrouting base chains.
 Therefore we also need to keep record of the base chain context (type, hooknum) and revalidate if the
 chain becomes reachable from a different hook location. (CVE-2025-71160)

Solution

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

See Also

https://advisory.echohq.com/cve/CVE-2025-71160

Plugin Details

Severity: Medium

ID: 461166

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.46

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-2025-71160

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: 1/24/2026

Vulnerability Publication Date: 1/23/2026

Reference Information

CVE: CVE-2025-71160