linux-cve-announce - CVE-2026-23075: can: esd_usb: esd_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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2026020419-CVE-2026-23075-0aef@gregkh>
Date: Wed,  4 Feb 2026 17:14:34 +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-23075: can: esd_usb: esd_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: esd_usb: esd_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 esd_usb_open(), the URBs for USB-in transfers are allocated, added to
the dev->rx_submitted anchor and submitted. In the complete callback
esd_usb_read_bulk_callback(), the URBs are processed and resubmitted. In
esd_usb_close() 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 esd_usb_close().

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

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

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

	Issue introduced in 2.6.36 with commit 96d8e90382dc336b5de401164597edfdc2e8d9f1 and fixed in 6.6.122 with commit adec5e1f9c99fe079ec4c92cca3f1109a3e257c3
	Issue introduced in 2.6.36 with commit 96d8e90382dc336b5de401164597edfdc2e8d9f1 and fixed in 6.12.68 with commit 9d1807b442fc3286b204f8e59981b10e743533ce
	Issue introduced in 2.6.36 with commit 96d8e90382dc336b5de401164597edfdc2e8d9f1 and fixed in 6.18.8 with commit a9503ae43256e80db5cba9d449b238607164c51d
	Issue introduced in 2.6.36 with commit 96d8e90382dc336b5de401164597edfdc2e8d9f1 and fixed in 6.19-rc7 with commit 5a4391bdc6c8357242f62f22069c865b792406b3

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-23075
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/esd_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/adec5e1f9c99fe079ec4c92cca3f1109a3e257c3
	https://git.kernel.org/stable/c/9d1807b442fc3286b204f8e59981b10e743533ce
	https://git.kernel.org/stable/c/a9503ae43256e80db5cba9d449b238607164c51d
	https://git.kernel.org/stable/c/5a4391bdc6c8357242f62f22069c865b792406b3