Description
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.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Linux | Linux | 6.1 | 6.1.191 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | linux | 6.4.11-1 | — |
| Debian 13 | linux | 6.4.11-1 | — |
| Debian 12 | linux | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 24.04 LTS | linux-intel +9 | No fix yet | — |
| Ubuntu 22.04 LTS | linux-riscv +32 | No fix yet | — |
| Ubuntu 20.04 LTS | linux-gke +28 | No fix yet | — |
| Ubuntu 18.04 LTS | linux-gcp +14 | No fix yet | — |
| Ubuntu 16.04 LTS | linux-hwe-edge | No fix yet | — |
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP7 | kernel-64kb +6 | 6.4.0-150700.53.22.1 | SUSE-SU-2025:4057-1 |
| SLES 15 SP7 | kernel-azure +2 | 6.4.0-150700.20.18.1 | SUSE-SU-2025:4132-1 |
| SLES 15 SP7 | kernel-default-base | 6.4.0-150700.53.22.1.150700.17.15.1 | SUSE-SU-2025:4057-1 |
| SLES 15 SP6 | kernel-64kb +6 | 6.4.0-150600.23.73.1 | SUSE-SU-2025:03600-1 |
| SLES 15 SP6 | kernel-azure +2 | 6.4.0-150600.8.52.1 | SUSE-SU-2025:03634-1 |
| SLES 15 SP6 | kernel-default-base | 6.4.0-150600.23.73.1.150600.12.32.1 | SUSE-SU-2025:03600-1 |
Show 6 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLE Micro 6.1 | kernel-default-base | 6.4.0-35.1.21.12 | SUSE-SU-2025:20861-1 |
| SLE Micro 6.1 | kernel-rt +1 | 6.4.0-37.1 | SUSE-SU-2025:20898-1 |
| SLE Micro 6.1 | kernel-source +2 | 6.4.0-35.1 | SUSE-SU-2025:20861-1 |
| SLE Micro 6.0 | kernel-default-base | 6.4.0-35.1.21.12 | SUSE-SU-2025:20851-1 |
| SLE Micro 6.0 | kernel-rt +1 | 6.4.0-37.1 | SUSE-SU-2025:20870-1 |
| SLE Micro 6.0 | kernel-source +2 | 6.4.0-35.1 | SUSE-SU-2025:20851-1 |
| SLE Live Patching 15 SP7 | kernel-default | 6.4.0-150700.53.22.1 | SUSE-SU-2025:4057-1 |
| SLE Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7-RT_Update_6 | 1-150700.1.3.1 | SUSE-SU-2025:4141-1 |
| SLE Live Patching 15 SP7 | kernel-livepatch-SLE15-SP7_Update_6 | 1-150700.15.3.1 | SUSE-SU-2025:4057-1 |
| SLE Live Patching 15 SP6 | kernel-default | 6.4.0-150600.23.73.1 | SUSE-SU-2025:03600-1 |
| SLE Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_16 | 1-150600.1.3.1 | SUSE-SU-2025:3751-1 |
| SLE Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_16 | 1-150600.13.3.1 | SUSE-SU-2025:03600-1 |
| SUSE Real Time Module 15 SP7 | kernel-rt +2 | 6.4.0-150700.7.22.1 | SUSE-SU-2025:4141-1 |
| SUSE Real Time Module 15 SP6 | kernel-rt +3 | 6.4.0-150600.10.55.1 | SUSE-SU-2025:3751-1 |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Leap 15.6 | dtb-aarch64 +10 | 6.4.0-150600.23.73.1 | SUSE-SU-2025:03600-1 |
| openSUSE Leap 15.6 | kernel-azure +2 | 6.4.0-150600.8.52.1 | SUSE-SU-2025:03634-1 |
| openSUSE Leap 15.6 | kernel-default-base | 6.4.0-150600.23.73.1.150600.12.32.1 | SUSE-SU-2025:03600-1 |
| openSUSE Leap 15.6 | kernel-rt +3 | 6.4.0-150600.10.55.1 | SUSE-SU-2025:3751-1 |
Advisories 11
- WID-SEC-2025-2187 Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service BSI CERT-Bund (WID) · Oct 18, 2026
- SUSE-SU-2025:20851-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Mar 23, 2026
- SUSE-SU-2025:03634-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Mar 23, 2026
- SUSE-SU-2025:4141-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Mar 23, 2026
- SUSE-SU-2025:20861-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Mar 23, 2026
- SUSE-SU-2025:20870-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Mar 23, 2026
- SUSE-SU-2025:03600-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Mar 23, 2026
- SUSE-SU-2025:20898-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Mar 23, 2026
- SUSE-SU-2025:3751-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026
- SUSE-SU-2025:4132-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026
- SUSE-SU-2025:4057-1 Security update for the Linux Kernel SUSE / openSUSE Security Updates · Feb 4, 2026