linux-cve-announce - CVE-2025-68307: can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025121645-CVE-2025-68307-5e9b@gregkh>
Date: Tue, 16 Dec 2025 16:07:01 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68307: can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs

The driver lacks the cleanup of failed transfers of URBs. This reduces the
number of available URBs per error by 1. This leads to reduced performance
and ultimately to a complete stop of the transmission.

If the sending of a bulk URB fails do proper cleanup:
- increase netdev stats
- mark the echo_sbk as free
- free the driver's context and do accounting
- wake the send queue

The Linux kernel CVE team has assigned CVE-2025-68307 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 3.16 with commit d08e973a77d128b25e01a08c34d89593fdf222da and fixed in 6.1.159 with commit f7a5560675bd85efaf16ab01a43053670ff2b000
	Issue introduced in 3.16 with commit d08e973a77d128b25e01a08c34d89593fdf222da and fixed in 6.6.119 with commit 1a588c40a422a3663a52f1c5535e8fb6b044167d
	Issue introduced in 3.16 with commit d08e973a77d128b25e01a08c34d89593fdf222da and fixed in 6.12.61 with commit 4a82072e451eacf24fc66a445e906f5095d215db
	Issue introduced in 3.16 with commit d08e973a77d128b25e01a08c34d89593fdf222da and fixed in 6.17.11 with commit 9c8eb33b7008178b6ce88aa7593d12063ce60ca3
	Issue introduced in 3.16 with commit d08e973a77d128b25e01a08c34d89593fdf222da and fixed in 6.18 with commit 516a0cd1c03fa266bb67dd87940a209fd4e53ce7

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-68307
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/can/usb/gs_usb.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/f7a5560675bd85efaf16ab01a43053670ff2b000
	https://git.kernel.org/stable/c/1a588c40a422a3663a52f1c5535e8fb6b044167d
	https://git.kernel.org/stable/c/4a82072e451eacf24fc66a445e906f5095d215db
	https://git.kernel.org/stable/c/9c8eb33b7008178b6ce88aa7593d12063ce60ca3
	https://git.kernel.org/stable/c/516a0cd1c03fa266bb67dd87940a209fd4e53ce7