linux-cve-announce - CVE-2026-23058: can: ems_usb: ems_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: <2026020414-CVE-2026-23058-802c@gregkh>
Date: Wed,  4 Feb 2026 17:14:17 +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-23058: can: ems_usb: ems_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: ems_usb: ems_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 ems_usb_open(), the URBs for USB-in transfers are allocated, added to
the dev->rx_submitted anchor and submitted. In the complete callback
ems_usb_read_bulk_callback(), the URBs are processed and resubmitted. In
ems_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 ems_usb_close().

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

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

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

	Issue introduced in 2.6.32 with commit 702171adeed3607ee9603ec30ce081411e36ae42 and fixed in 6.6.122 with commit e9410fdd4d5f7eaa6526d8c80e83029d7c86a8e8
	Issue introduced in 2.6.32 with commit 702171adeed3607ee9603ec30ce081411e36ae42 and fixed in 6.12.68 with commit 46a191ff7eeec33a2ccb2a1bfea34e18fbc5dc1a
	Issue introduced in 2.6.32 with commit 702171adeed3607ee9603ec30ce081411e36ae42 and fixed in 6.18.8 with commit 68c62b3e53901846b5f68c5a8bade72a5d9c0b87
	Issue introduced in 2.6.32 with commit 702171adeed3607ee9603ec30ce081411e36ae42 and fixed in 6.19-rc7 with commit 0ce73a0eb5a27070957b67fd74059b6da89cc516

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-23058
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/ems_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/e9410fdd4d5f7eaa6526d8c80e83029d7c86a8e8
	https://git.kernel.org/stable/c/46a191ff7eeec33a2ccb2a1bfea34e18fbc5dc1a
	https://git.kernel.org/stable/c/68c62b3e53901846b5f68c5a8bade72a5d9c0b87
	https://git.kernel.org/stable/c/0ce73a0eb5a27070957b67fd74059b6da89cc516