LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23080: can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak

In the Linux kernel, the following vulnerability has been resolved: can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"). In mcba_usb_probe() -> mcba_usb_start(), the URBs for USB-in transfers are allocated, added to the priv->rx_submitted anchor and submitted. In the complete callback mcba_usb_read_bulk_callback(), the URBs are processed and resubmitted. In mcba_usb_close() -> mcba_urb_unlink() the URBs are freed by calling usb_kill_anchored_urbs(&priv->rx_submitted). However, this does not take into account that the USB framework unanchors the URB before the complete function is called. This means that once an in-URB has been completed, it is no longer anchored and is ultimately not released in usb_kill_anchored_urbs(). Fix the memory leak by anchoring the URB in the mcba_usb_read_bulk_callback()to the priv->rx_submitted anchor.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23080 is a Linux kernel memory leak in the mcba_usb CAN USB driver. Completed USB receive requests can become unanchored before cleanup, so memory is not released as expected. The public record does not provide CVSS, impact scope, or exploitation evidence.

Executive priority

Treat as a targeted kernel maintenance issue. It is most urgent for embedded, industrial, automotive, or lab systems using CAN USB interfaces, where memory leaks can affect availability over time.

Technical view

The issue is in mcba_usb_read_bulk_callback(). USB-in URBs are allocated, anchored, submitted, processed, and resubmitted, but the USB framework unanchors an URB before the completion callback. Cleanup via usb_kill_anchored_urbs() can miss completed URBs, causing a leak. The fix reanchors the URB in the callback.

Likely exposure

Exposure appears limited to Linux systems using the mcba_usb CAN USB driver path. The CVE record lists Linux kernel versions/series including 4.12, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, and 6.19.

Exploitation context

No cited source states active exploitation, public exploit availability, or KEV listing. The available evidence supports a kernel driver memory leak and associated stability risk, not remote code execution or privilege escalation.

Researcher notes

The record does not include CVSS, CWE, exploitability details, or a complete operational impact analysis. Analysis should stay close to the driver lifecycle: URB anchoring, completion callback behavior, and cleanup through usb_kill_anchored_urbs().

Mitigation direction

  • Check Linux vendor guidance for fixed kernel packages covering CVE-2026-23080.
  • Prioritize updates on hosts using CAN USB hardware and the mcba_usb driver.
  • Apply the relevant stable kernel fix from your distribution or kernel source.
  • If updates are delayed, reduce use of affected CAN USB paths where operationally feasible.

Validation and detection

  • Inventory Linux hosts and kernel versions against the CVE affected version list.
  • Check whether mcba_usb is built, loaded, or required on each host.
  • Confirm installed kernel includes the relevant stable commit for its branch.
  • Monitor affected systems for abnormal kernel memory growth during CAN USB activity.
Prepared
Confidence
medium
Sources
9

Public sources used

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-23080 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux51f3baad7de943780ce0c17bd7975df567dd6e14, 51f3baad7de943780ce0c17bd7975df567dd6e14, 51f3baad7de943780ce0c17bd7975df567dd6e14, 51f3baad7de943780ce0c17bd7975df567dd6e14, 51f3baad7de943780ce0c17bd7975df567dd6e14, 51f3baad7de943780ce0c17bd7975df567dd6e14, 51f3baad7de943780ce0c17bd7975df567dd6e14unaffected
LinuxLinux4.12, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.