Detections
Analytics

Echo: linux: security update to 6.4.11-1

medium Tenable Cloud Security Plugin ID 460851

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: can: gs_usb: fix time stamp counter
 initialization If the gs_usb device driver is unloaded (or unbound) before the interface is shut down, the
 USB stack first calls the struct usb_driver::disconnect and then the struct net_device_ops::ndo_stop
 callback. In gs_usb_disconnect() all pending bulk URBs are killed, i.e. no more RX'ed CAN frames are send
 from the USB device to the host. Later in gs_can_close() a reset control message is send to each CAN
 channel to remove the controller from the CAN bus. In this race window the USB device can still receive
 CAN frames from the bus and internally queue them to be send to the host. At least in the current version
 of the candlelight firmware, the queue of received CAN frames is not emptied during the reset command.
 After loading (or binding) the gs_usb driver, new URBs are submitted during the struct
 net_device_ops::ndo_open callback and the candlelight firmware starts sending its already queued CAN
 frames to the host. However, this scenario was not considered when implementing the hardware timestamp
 function. The cycle counter/time counter infrastructure is set up (gs_usb_timestamp_init()) after the USBs
 are submitted, resulting in a NULL pointer dereference if timecounter_cyc2time() (via the call chain:
 gs_usb_receive_bulk_callback() -> gs_usb_set_timestamp() -> gs_usb_skb_set_timestamp()) is called too
 early. Move the gs_usb_timestamp_init() function before the URBs are submitted to fix this problem. For a
 comprehensive solution, we need to consider gs_usb devices with more than 1 channel. The cycle
 counter/time counter infrastructure is setup per channel, but the RX URBs are per device. Once
 gs_can_open() of _a_ channel has been called, and URBs have been submitted, the
 gs_usb_receive_bulk_callback() can be called for _all_ available channels, even for channels that are not
 running, yet. As cycle counter/time counter has not set up, this will again lead to a NULL pointer
 dereference. Convert the cycle counter/time counter from a "per channel" to a "per device" functionality.
 Also set it up, before submitting any URBs to the device. Further in gs_usb_receive_bulk_callback(), don't
 process any URBs for not started CAN channels, only resubmit the URB. (CVE-2023-53523)

Solution

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

See Also

https://advisory.echohq.com/cve/CVE-2023-53523

Plugin Details

Severity: Medium

ID: 460851

Version: Revision 1.1

Type: Local

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.15

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-2023-53523

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: 10/22/2025

Vulnerability Publication Date: 10/1/2025

Reference Information

CVE: CVE-2023-53523