Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Fixed version: Linux Linux 611e839d2d552416b498ed5593e10670f61fcd4d, 6c5124a60989051799037834f0a1a4b428718157, 97250eb05e4b6afe787290e8fd97d0675116c61b.

Low priority for now. Upgrade to Linux Linux 611e839d2d552416b498ed5593e10670f61fcd4d, 6c5124a60989051799037834f0a1a4b428718157, 97250eb05e4b6afe787290e8fd97d0675116c61b or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Jan 31, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23037

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.13affected
    • 8537257874e949a59c834cecfd5a063e11b64b0b and later · before 97250eb05e4b6afe787290e8fd97d0675116c61baffected · git
    • 8537257874e949a59c834cecfd5a063e11b64b0b and later · before aec888f44853584b5a7cd01249806030cf94a73daffected · git
    • 8537257874e949a59c834cecfd5a063e11b64b0b and later · before 611e839d2d552416b498ed5593e10670f61fcd4daffected · git
    • 8537257874e949a59c834cecfd5a063e11b64b0b and later · before ba45e3d6b02c97dbb4578fbae7027fd66f3caa10affected · git
    • 8537257874e949a59c834cecfd5a063e11b64b0b and later · before 6c5124a60989051799037834f0a1a4b428718157affected · git
    • 8537257874e949a59c834cecfd5a063e11b64b0b and later · before b1979778e98569c1e78c2c7f16bb24d76541ab00affected · git
    • before 5.13not affected · semver
    • 5.15.199 and later · up to and including 5.15.*not affected · semver
    • 6.1.162 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-23034Jan 31, 2026 · drm/amdgpu/userq: Fix fence reference leak on queue teardown v2
    0Monitor
  • ← EarlierCVE-2026-23036Jan 31, 2026 · btrfs: release path before iget_failed() in btrfs_read_locked_inode()
    0Monitor
  • Later →CVE-2026-23039Jan 31, 2026 · drm/gud: fix NULL fb and crtc dereferences on USB disconnect
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux611e839d2d552416b498ed5593e10670f61fcd4dVendor (CNA)
Linux Linux6c5124a60989051799037834f0a1a4b428718157Vendor (CNA)
Linux Linux97250eb05e4b6afe787290e8fd97d0675116c61bVendor (CNA)
Linux Linuxaec888f44853584b5a7cd01249806030cf94a73dVendor (CNA)
Linux Linuxb1979778e98569c1e78c2c7f16bb24d76541ab00Vendor (CNA)
Linux Linuxba45e3d6b02c97dbb4578fbae7027fd66f3caa10Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records