CVE-2026-23324: can: usb: etas_es58x: correctly anchor the urb in the read bulk callback
In the Linux kernel, the following vulnerability has been resolved:
can: usb: etas_es58x: correctly anchor the urb in the read bulk callback
When submitting an urb, that is using the anchor pattern, it needs to be
anchored before submitting it otherwise it could be leaked if
usb_kill_anchored_urbs() is called. This logic is correctly done
elsewhere in the driver, except in the read bulk callback so do that
here also.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23324 is a Linux kernel driver bug affecting ETAS ES58x USB CAN adapter handling. The issue can leak a USB request during cleanup or error handling. Business urgency depends on whether affected Linux systems use this specific CAN USB driver. No CVSS score, CWE, or exploitation evidence is provided.
Executive priority
Track and remediate through normal Linux kernel patch management unless ETAS ES58x USB CAN adapters are used in operational environments. Escalate priority for industrial, lab, automotive, or embedded systems where CAN availability matters and kernel update windows are constrained.
Technical view
In the Linux kernel etas_es58x CAN USB driver, the read bulk callback submitted an URB before anchoring it. If usb_kill_anchored_urbs() ran during that window, the URB could be leaked. The stable fixes align this path with the driver's existing anchor-before-submit pattern.
Likely exposure
Exposure appears limited to Linux systems with affected kernel builds where the ETAS ES58x USB CAN driver is present and used. The source bundle lists Linux as affected across multiple kernel version lines, but distribution backport status must be confirmed separately.
Exploitation context
The bundle does not report active exploitation, public exploit use, KEV listing, CVSS, or practical impact beyond an URB leak. Treat exploitation status as unproven. Operational impact is more plausible for systems using CAN bus tooling or embedded/industrial Linux deployments with ETAS ES58x hardware.
Researcher notes
The evidence supports a kernel driver resource-management flaw, not a demonstrated privilege escalation or remote attack. The affected-version data is broad and commit-based, so researchers should validate exact kernel lineage and downstream backports before declaring exposure.
Mitigation direction
Update affected Linux kernels through the distribution or vendor security channel.
Confirm the update contains one of the referenced stable kernel fixes.
Check vendor guidance if no patched kernel package is available.
Prioritize systems using ETAS ES58x USB CAN adapters or related CAN workflows.
Validation and detection
Inventory Linux kernel versions across relevant fleets.
Identify systems where the etas_es58x driver is built, loadable, or in use.
Compare kernel package changelogs against the referenced stable commits.
Confirm distribution advisories for backported fixes before marking systems remediated.
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-23324 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
0ADP 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.
Mar 25, 2026, 10:27 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.