CVE-2026-23037: can: etas_es58x: allow partial RX URB allocation to succeed
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().
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a resource leak in the ETAS ES58x CAN USB driver. Under memory pressure, opening the driver after only some receive URBs are allocated can leak kernel USB resources. The provided sources do not show code execution, privilege escalation, or active exploitation.
Executive priority
Treat as targeted patch hygiene for systems using Linux CAN/USB interfaces, especially operational or test environments. It does not currently justify emergency response based on the provided evidence, but affected kernels should enter the normal security update cycle.
Technical view
In es58x_alloc_rx_urbs(), partial RX URB allocation was incorrectly treated as fatal. es58x_open() then returned early without reaching the free_urbs cleanup path, leaving anchored URBs leaked. The fix restores intended partial-allocation handling by returning success when at least one URB was allocated.
Likely exposure
Exposure appears limited to Linux systems with affected kernels where the etas_es58x CAN driver is present and used. Practical impact depends on deployed kernel versions, distribution backports, and whether ETAS ES58x CAN USB functionality is enabled.
Exploitation context
The bundle reports KEV false and provides no evidence of public exploitation. The described failure requires a partial URB allocation condition during driver open, suggesting a reliability or denial-of-service concern rather than a confirmed remote compromise path.
Researcher notes
The key behavior is a cleanup bypass after partial allocation. Sources identify stable kernel commits and a Siemens advisory, but provide no CVSS, CWE, exploitability assessment, or detailed product impact beyond Linux kernel affected ranges.
Mitigation direction
Update to a Linux kernel build containing the referenced stable fixes.
Check Linux distribution advisories for backported packages covering CVE-2026-23037.
Review the Siemens advisory for product-specific guidance where applicable.
If unused, disable or remove ETAS ES58x CAN USB driver exposure per vendor guidance.
Validation and detection
Inventory Linux kernel versions against vendor-fixed builds and backport notices.
Check whether the etas_es58x driver is loaded or available on relevant systems.
Confirm patched kernels include one of the referenced stable commits or equivalent backport.
Review crash, USB, or CAN driver logs for repeated allocation failures or open errors.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23037 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
8Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jan 31, 2026, 11:42 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.