# CVE-2026-23037: can: etas_es58x: allow partial RX URB allocation to succeed

> A memory leak in the Linux kernel CAN driver allows attackers to cause denial of service by triggering partial URB allocation failures.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2026
- **Updated:** 2 Jun 2026
- **Also known as:** BELL-CVE-2026-23037, DEBIAN-CVE-2026-23037, GHSA-35c8-wvgc-32mg, ROOT-OS-DEBIAN-12-CVE-2026-23037, ROOT-OS-DEBIAN-13-CVE-2026-23037, ROOT-OS-UBUNTU-2204-CVE-2026-23037, ROOT-OS-UBUNTU-2404-CVE-2026-23037, UBUNTU-CVE-2026-23037

## What is CVE-2026-23037?

CVE-2026-23037 is a memory corruption vulnerability in Linux, published on 31 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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().

## Which versions are affected by CVE-2026-23037?


## How do I fix CVE-2026-23037?

Apply the vendor's patch.

## Is CVE-2026-23037 being exploited?

There is no known exploitation of CVE-2026-23037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23037 and fix it if it is affected.

What it is: CVE-2026-23037 is a memory corruption vulnerability in Linux, published on 31 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23037 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23037/ (Markdown: https://insights.sbomify.com/CVE-2026-23037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23037
- OSV: https://osv.dev/vulnerability/CVE-2026-23037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23037/
Summaries are generated and may contain mistakes; the official description above is the record.