linux-cve-announce - CVE-2026-23037: can: etas_es58x: allow partial RX URB allocation to succeed

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: <2026013122-CVE-2026-23037-6cae@gregkh>
Date: Sat, 31 Jan 2026 12:44:37 +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-23037: can: etas_es58x: allow partial RX URB allocation to succeed

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

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

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

can: etas_es58x: allow partial RX URB allocation to succeed

When es58x_alloc_rx_urbs() fails to allocate the requested number of
URBs but succeeds in allocating some, it returns an error code.
This causes es58x_open() to return early, skipping the cleanup label
'free_urbs', which leads to the anchored URBs being leaked.

As pointed out by maintainer Vincent Mailhol, the driver is designed
to handle partial URB allocation gracefully. Therefore, partial
allocation should not be treated as a fatal error.

Modify es58x_alloc_rx_urbs() to return 0 if at least one URB has been
allocated, restoring the intended behavior and preventing the leak
in es58x_open().

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


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

	Issue introduced in 5.13 with commit 8537257874e949a59c834cecfd5a063e11b64b0b and fixed in 6.6.122 with commit 611e839d2d552416b498ed5593e10670f61fcd4d
	Issue introduced in 5.13 with commit 8537257874e949a59c834cecfd5a063e11b64b0b and fixed in 6.12.67 with commit ba45e3d6b02c97dbb4578fbae7027fd66f3caa10
	Issue introduced in 5.13 with commit 8537257874e949a59c834cecfd5a063e11b64b0b and fixed in 6.18.7 with commit 6c5124a60989051799037834f0a1a4b428718157
	Issue introduced in 5.13 with commit 8537257874e949a59c834cecfd5a063e11b64b0b and fixed in 6.19-rc6 with commit b1979778e98569c1e78c2c7f16bb24d76541ab00

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-23037
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/etas_es58x/es58x_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/611e839d2d552416b498ed5593e10670f61fcd4d
	https://git.kernel.org/stable/c/ba45e3d6b02c97dbb4578fbae7027fd66f3caa10
	https://git.kernel.org/stable/c/6c5124a60989051799037834f0a1a4b428718157
	https://git.kernel.org/stable/c/b1979778e98569c1e78c2c7f16bb24d76541ab00