CVE-2026-74459

can: etas_es58x: es58x_read_bulk_callback(): fix RX buffer leak on URB resubmit failure

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.19.75.15.203 ≤ v < 5.15.2166.1.167 ≤ v < 6.1.1836.12.77 ≤ v < 6.12.1036.18.17 ≤ v < 6.18.446.19.7 ≤ v < 6.206.6.130 ≤ v < 6.6.1517.0 ≤ v < 7.1.87.0 ≤ v < 7.218eee279e9b5bff0db1aca9475ae4bc12804f05c2185ea6e4ebcb61d1224dc7d187c59723cb5ad595.15.2035eaad4f768266f1f17e01232ffe2ef009f8129b76.1.1676.12.776.18.176.19.76.6.1307.07a0171b4921ad443fee5ed4fcb9d99fa4776edacb878444519fa03a3edd287d1963cf79ef78be2f1b8f9ca88253574638bcff38900a4c28d570b1919f6e90c113c92e83fc0963d5e60e16b0e8a268981
Vendor states this is fixed in 0ef136ba052101243ba117a1aca6f4a4c3a81142 (fixed)
Vendor states this is fixed in 19c6c8c6cd5dd14fab5fcd744584812a57cbb78d (fixed)
Vendor states this is fixed in 21da1a374769751546cc131e58a4d8bd968f57b2 (fixed)
Vendor states this is fixed in 7a0cf2b2497c757c3cb1286eddf2986abb0d387b (fixed)
Vendor states this is fixed in b85e5c310382803d27adf6fe6554d4208bc8951c (fixed)
Vendor states this is fixed in c311f17c261fd375ddf5755f2ebe1f022c19c5b0 (fixed)
Vendor states this is fixed in c7ddf119544eea2d8409e12471c3f9f36ca02e3f (fixed)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card