Detections
Analytics

Echo: linux: security update to 6.1.170-1

medium Tenable Self-Hosted Container Security Plugin ID 461622

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: dsa: improve shutdown sequence
 Alexander Sverdlin presents 2 problems during shutdown with the lan9303 driver. One is specific to lan9303
 and the other just happens to reproduce there. The first problem is that lan9303 is unique among DSA
 drivers in that it calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown, not remove):
 phy_state_machine() -> ... -> dsa_user_phy_read() -> ds->ops->phy_read() -> lan9303_phy_read() ->
 chip->ops->phy_read() -> lan9303_mdio_phy_read() -> dev_get_drvdata() But we never stop the
 phy_state_machine(), so it may continue to run after dsa_switch_shutdown(). Our common pattern in all DSA
 drivers is to set drvdata to NULL to suppress the remove() method that may come afterwards. But in this
 case it will result in an NPD. The second problem is that the way in which we set dp->conduit->dsa_ptr =
 NULL; is concurrent with receive packet processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is
 NULL, but afterwards, rather than continuing to use that non-NULL value, dev->dsa_ptr is dereferenced
 again and again without NULL checks: dsa_conduit_find_user() and many other places. In between
 dereferences, there is no locking to ensure that what was valid once continues to be valid. Both problems
 have the common aspect that closing the conduit interface solves them. In the first case,
 dev_close(conduit) triggers the NETDEV_GOING_DOWN event in dsa_user_netdevice_event() which closes user
 ports as well. dsa_port_disable_rt() calls phylink_stop(), which synchronously stops the phylink state
 machine, and ds->ops->phy_read() will thus no longer call into the driver after this point. In the second
 case, dev_close(conduit) should do this, as per Documentation/networking/driver.rst: | Quiescence |
 ---------- | | After the ndo_stop routine has been called, the hardware must | not receive or transmit any
 data. All in flight packets must | be aborted. If necessary, poll or wait for completion of | any reset
 commands. So it should be sufficient to ensure that later, when we zeroize conduit->dsa_ptr, there will be
 no concurrent dsa_switch_rcv() call on this conduit. The addition of the netif_device_detach() function is
 to ensure that ioctls, rtnetlinks and ethtool requests on the user ports no longer propagate down to the
 driver - we're no longer prepared to handle them. The race condition actually did not exist when commit
 0650bf52b31f ("net: dsa: be compatible with masters which unregister on shutdown") first introduced
 dsa_switch_shutdown(). It was created later, when we stopped unregistering the user interfaces from a bad
 spot, and we just replaced that sequence with a racy zeroization of conduit->dsa_ptr (one which doesn't
 ensure that the interfaces aren't up). (CVE-2024-49998)

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-2024-49998

Plugin Details

Severity: Medium

ID: 461622

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.18

CVSS v2

Risk Factor: Low

Base Score: 3.8

Temporal Score: 2.8

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

CVSS Score Source: CVE-2024-49998

CVSS v3

Risk Factor: Medium

Base Score: 4.7

Temporal Score: 4.1

Vector: CVSS:3.0/AV:L/AC:H/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: 9/15/2025

Vulnerability Publication Date: 10/21/2024

Reference Information

CVE: CVE-2024-49998