linux-cve-announce - CVE-2026-23061: can: kvaser_usb: kvaser_usb_read_bulk

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2026020415-CVE-2026-23061-31be@gregkh>
Date: Wed,  4 Feb 2026 17:14:20 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23061: can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak

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

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

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

can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak

Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb:
gs_usb_receive_bulk_callback(): fix URB memory leak").

In kvaser_usb_set_{,data_}bittiming() -> kvaser_usb_setup_rx_urbs(), the
URBs for USB-in transfers are allocated, added to the dev->rx_submitted
anchor and submitted. In the complete callback
kvaser_usb_read_bulk_callback(), the URBs are processed and resubmitted. In
kvaser_usb_remove_interfaces() the URBs are freed by calling
usb_kill_anchored_urbs(&dev->rx_submitted).

However, this does not take into account that the USB framework unanchors
the URB before the complete function is called. This means that once an
in-URB has been completed, it is no longer anchored and is ultimately not
released in usb_kill_anchored_urbs().

Fix the memory leak by anchoring the URB in the
kvaser_usb_read_bulk_callback() to the dev->rx_submitted anchor.

The Linux kernel CVE team has assigned CVE-2026-23061 to this issue.

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

	Issue introduced in 3.8 with commit 080f40a6fa28dab299da7a652e444b1e2d9231e7 and fixed in 6.6.122 with commit 7c308f7530bffafa994e0aa8dc651a312f4b9ff4
	Issue introduced in 3.8 with commit 080f40a6fa28dab299da7a652e444b1e2d9231e7 and fixed in 6.12.68 with commit 94a7fc42e21c7d9d1c49778cd1db52de5df52a01
	Issue introduced in 3.8 with commit 080f40a6fa28dab299da7a652e444b1e2d9231e7 and fixed in 6.18.8 with commit 3b1a593eab941c3f32417896cc7df564191f2482
	Issue introduced in 3.8 with commit 080f40a6fa28dab299da7a652e444b1e2d9231e7 and fixed in 6.19-rc7 with commit 248e8e1a125fa875158df521b30f2cc7e27eeeaa

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-2026-23061
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/kvaser_usb/kvaser_usb_core.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/7c308f7530bffafa994e0aa8dc651a312f4b9ff4
	https://git.kernel.org/stable/c/94a7fc42e21c7d9d1c49778cd1db52de5df52a01
	https://git.kernel.org/stable/c/3b1a593eab941c3f32417896cc7df564191f2482
	https://git.kernel.org/stable/c/248e8e1a125fa875158df521b30f2cc7e27eeeaa