Detections
Analytics

Echo: linux: security update to 6.1.176-1

medium Tenable Self-Hosted Container Security Plugin ID 464360

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: slimbus: qcom-ngd-ctrl: Avoid ABBA on
 tx_lock/ctrl->lock During the SSR/PDR down notification the tx_lock is taken with the intent to provide
 synchronization with active DMA transfers. But during this period qcom_slim_ngd_down() is invoked, which
 ends up in slim_report_absent(), which takes the slim_controller lock. In multiple other codepaths these
 two locks are taken in the opposite order (i.e. slim_controller then tx_lock). The result is a lockdep
 splat, and a possible deadlock: rprocctl/449 is trying to acquire lock: ffff00009793e620
 (&ctrl->lock){+.+.}-{4:4}, at: slim_report_absent (drivers/slimbus/core.c:322) slimbus but task is already
 holding lock: ffff00009793fb50 (&ctrl->tx_lock){+.+.}-{4:4}, at: qcom_slim_ngd_ssr_pdr_notify
 (drivers/slimbus/qcom-ngd-ctrl.c:1475) slim_qcom_ngd_ctrl which lock already depends on the new lock.
 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ctrl->tx_lock); lock(&ctrl->lock);
 lock(&ctrl->tx_lock); lock(&ctrl->lock); The assumption is that the comment refers to the desire to not
 call qcom_slim_ngd_exit_dma() while we have an ongoing DMA TX transaction. But any such transaction is
 initiated and completed within a single qcom_slim_ngd_xfer_msg(). Prior to calling
 qcom_slim_ngd_exit_dma() the slim_controller is torn down, all child devices are notified that the slimbus
 is gone and the child devices are removed. Stop taking the tx_lock in qcom_slim_ngd_ssr_pdr_notify() to
 avoid the deadlock. (CVE-2026-53331)

Solution

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

See Also

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

Plugin Details

Severity: Medium

ID: 464360

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.63

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

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: 7/2/2026

Vulnerability Publication Date: 7/1/2026

Reference Information

CVE: CVE-2026-53331