Detections
Analytics

Echo: linux: security update to 6.1.162-1

medium Tenable Self-Hosted Container Security Plugin ID 459845

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: nfc: fix deadlock between
 nfc_unregister_device and rfkill_fop_write A deadlock can occur between nfc_unregister_device() and
 rfkill_fop_write() due to lock ordering inversion between device_lock and rfkill_global_mutex. The
 problematic lock order is: Thread A (rfkill_fop_write): rfkill_fop_write()
 mutex_lock(&rfkill_global_mutex) rfkill_set_block() nfc_rfkill_set_block() nfc_dev_down()
 device_lock(&dev->dev) <- waits for device_lock Thread B (nfc_unregister_device): nfc_unregister_device()
 device_lock(&dev->dev) rfkill_unregister() mutex_lock(&rfkill_global_mutex) <- waits for
 rfkill_global_mutex This creates a classic ABBA deadlock scenario. Fix this by moving rfkill_unregister()
 and rfkill_destroy() outside the device_lock critical section. Store the rfkill pointer in a local
 variable before releasing the lock, then call rfkill_unregister() after releasing device_lock. This change
 is safe because rfkill_fop_write() holds rfkill_global_mutex while calling the rfkill callbacks, and
 rfkill_unregister() also acquires rfkill_global_mutex before cleanup. Therefore, rfkill_unregister() will
 wait for any ongoing callback to complete before proceeding, and device_del() is only called after
 rfkill_unregister() returns, preventing any use-after-free. The similar lock ordering in
 nfc_register_device() (device_lock -> rfkill_global_mutex via rfkill_register) is safe because during
 registration the device is not yet in rfkill_list, so no concurrent rfkill operations can occur on this
 device. (CVE-2025-71079)

Solution

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

See Also

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

Plugin Details

Severity: Medium

ID: 459845

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.47

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

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/14/2026

Vulnerability Publication Date: 1/13/2026

Reference Information

CVE: CVE-2025-71079