LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23108: can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak

In the Linux kernel, the following vulnerability has been resolved: can: usb_8dev: usb_8dev_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 usb_8dev_open() -> usb_8dev_start(), the URBs for USB-in transfers are allocated, added to the priv->rx_submitted anchor and submitted. In the complete callback usb_8dev_read_bulk_callback(), the URBs are processed and resubmitted. In usb_8dev_close() -> unlink_all_urbs() 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 usb_8dev_read_bulk_callback() to the priv->rx_submitted anchor.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23108 is a Linux kernel memory leak in the usb_8dev CAN USB driver. It affects systems using this specific CAN adapter driver and can waste kernel memory during USB receive handling. The sources do not provide CVSS scoring, remote exploit claims, or business-impact details.

Executive priority

Treat as a targeted maintenance fix, not an emergency, unless usb_8dev CAN USB devices are deployed in critical environments. Patch through normal kernel update processes and confirm affected asset coverage.

Technical view

In usb_8dev_read_bulk_callback(), completed USB receive URBs are unanchored by the USB framework before callback processing. The close path frees anchored URBs, so completed URBs may escape cleanup. The fix re-anchors URBs to priv->rx_submitted in the callback, matching the described stable kernel commits.

Likely exposure

Exposure is likely limited to Linux systems with the usb_8dev CAN USB driver in use. The bundled affected data lists Linux kernel versions and stable-series boundaries, but distro-specific package exposure must be mapped through vendor kernel advisories.

Exploitation context

The bundle does not cite active exploitation, public exploit code, or CISA KEV listing. Practical abuse would depend on reaching the vulnerable driver path, likely through systems using the relevant USB CAN hardware or driver.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. No CWE, CVSS, exploit status, or detailed affected-version ranges beyond the provided bundle are available, so avoid over-scoping without distro validation.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check your Linux distribution advisory for the corrected package version.
  • Prioritize systems using usb_8dev CAN USB adapters or related lab/industrial hosts.
  • If no package is available, follow vendor guidance for temporary controls.

Validation and detection

  • Inventory kernels and confirm whether the usb_8dev driver is present or loaded.
  • Map running kernel builds to your distribution's CVE-2026-23108 advisory.
  • Verify updated kernels include one referenced stable commit or vendor backport.
  • Review kernel memory symptoms only as supporting evidence, not proof of exposure.
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-23108 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
LinuxLinux0024d8ad1639e32d717445c69ca813fd19c2a91c, 0024d8ad1639e32d717445c69ca813fd19c2a91c, 0024d8ad1639e32d717445c69ca813fd19c2a91c, 0024d8ad1639e32d717445c69ca813fd19c2a91c, 0024d8ad1639e32d717445c69ca813fd19c2a91c, 0024d8ad1639e32d717445c69ca813fd19c2a91c, 0024d8ad1639e32d717445c69ca813fd19c2a91cunaffected
LinuxLinux3.9, 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.