From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74459: can: etas_es58x: es58x_read_bulk_callback(): fix RX buffer leak on URB resubmit failure
Date: Sat, 15 Aug 2026 21:25:40 +0900 [thread overview]
Message-ID: <2026081532-CVE-2026-74459-bf7d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
can: etas_es58x: es58x_read_bulk_callback(): fix RX buffer leak on URB resubmit failure
es58x_read_bulk_callback() resubmits the RX URB after processing a received
packet. If the resubmit succeeds, the URB remains anchored and will be
handled by the normal RX path or by teardown.
However, if usb_submit_urb() fails, the callback unanchors the URB and then
returns directly. This skips the existing free_urb path, so the coherent
transfer buffer allocated with usb_alloc_coherent() is not released.
Reuse the existing free_urb path after a resubmit failure so that the RX
coherent buffer is freed before leaving the callback.
The Linux kernel CVE team has assigned CVE-2026-74459 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6.130 with commit f6e90c113c92e83fc0963d5e60e16b0e8a268981 and fixed in 6.6.151 with commit 0ef136ba052101243ba117a1aca6f4a4c3a81142
Issue introduced in 6.12.77 with commit b878444519fa03a3edd287d1963cf79ef78be2f1 and fixed in 6.12.103 with commit b85e5c310382803d27adf6fe6554d4208bc8951c
Issue introduced in 6.18.17 with commit 18eee279e9b5bff0db1aca9475ae4bc12804f05c and fixed in 6.18.44 with commit c311f17c261fd375ddf5755f2ebe1f022c19c5b0
Issue introduced in 7.0 with commit 5eaad4f768266f1f17e01232ffe2ef009f8129b7 and fixed in 7.1.8 with commit 19c6c8c6cd5dd14fab5fcd744584812a57cbb78d
Issue introduced in 7.0 with commit 5eaad4f768266f1f17e01232ffe2ef009f8129b7 and fixed in 7.2-rc6 with commit 7a0cf2b2497c757c3cb1286eddf2986abb0d387b
Issue introduced in 5.15.203 with commit 7a0171b4921ad443fee5ed4fcb9d99fa4776edac
Issue introduced in 6.1.167 with commit 2185ea6e4ebcb61d1224dc7d187c59723cb5ad59
Issue introduced in 6.19.7 with commit b8f9ca88253574638bcff38900a4c28d570b1919
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-74459
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/0ef136ba052101243ba117a1aca6f4a4c3a81142
https://git.kernel.org/stable/c/b85e5c310382803d27adf6fe6554d4208bc8951c
https://git.kernel.org/stable/c/c311f17c261fd375ddf5755f2ebe1f022c19c5b0
https://git.kernel.org/stable/c/19c6c8c6cd5dd14fab5fcd744584812a57cbb78d
https://git.kernel.org/stable/c/7a0cf2b2497c757c3cb1286eddf2986abb0d387b
reply other threads:[~2026-08-15 12:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081532-CVE-2026-74459-bf7d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.