CVE-2026-23037
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2026-01-31

Last updated on: 2026-02-06

Assigner: kernel.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().
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-31
Last Modified
2026-02-06
Generated
2026-05-07
AI Q&A
2026-01-31
EPSS Evaluated
2026-05-05
NVD
CVE-2026-23037
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
etas es58x *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability occurs in the Linux kernel's etas_es58x driver where the function es58x_alloc_rx_urbs() fails to handle partial allocation of RX URBs correctly. When it partially allocates URBs but not the full requested amount, it returns an error, causing es58x_open() to exit early and skip cleanup. This results in a memory leak of the allocated URBs. The fix changes es58x_alloc_rx_urbs() to return success if at least one URB is allocated, preventing the leak and restoring intended behavior.


How can this vulnerability impact me? :

The vulnerability can lead to a memory leak in the Linux kernel's etas_es58x driver due to improper handling of partial URB allocations. This leak could degrade system stability or performance over time if the leaked resources accumulate, potentially causing resource exhaustion or unexpected behavior in systems using this driver.


What immediate steps should I take to mitigate this vulnerability?

Update the Linux kernel to a version where the es58x_alloc_rx_urbs() function has been modified to return 0 if at least one URB has been allocated, preventing the URB leak. This fixes the issue by ensuring partial URB allocations are handled gracefully and the cleanup code is executed properly.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart