LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23061: can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak

In the Linux kernel, the following vulnerability has been resolved: can: kvaser_usb: kvaser_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 kvaser_usb_set_{,data_}bittiming() -> kvaser_usb_setup_rx_urbs(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback kvaser_usb_read_bulk_callback(), the URBs are processed and resubmitted. In kvaser_usb_remove_interfaces() the URBs are freed by calling usb_kill_anchored_urbs(&dev->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 kvaser_usb_read_bulk_callback() to the dev->rx_submitted anchor.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-23061 is a Linux kernel memory leak in the kvaser_usb CAN adapter driver. Systems using Kvaser USB CAN hardware may leak kernel memory while handling USB receive transfers. The source bundle provides no CVSS score, public exploitation evidence, or KEV listing.

Executive priority

Treat this as targeted operational risk, not broad internet-facing emergency. Patch through normal kernel maintenance, but prioritize industrial, automotive, lab, or embedded systems using Kvaser USB CAN adapters.

Technical view

The kvaser_usb read bulk completion callback processed and resubmitted URBs after the USB framework had unanchored them. The remove path only frees anchored URBs, so completed receive URBs could escape cleanup. Kernel stable commits fix this by re-anchoring the URB to dev->rx_submitted in the callback.

Likely exposure

Exposure is likely limited to Linux systems that load the kvaser_usb driver and use affected Kvaser USB CAN adapters. General servers without this hardware or driver path are unlikely to be exposed based on the provided sources.

Exploitation context

The CVE is not listed as KEV in the bundle, and no cited source reports active exploitation. The described condition is a kernel memory leak during normal driver receive-transfer handling, with practical relevance dependent on hardware and driver use.

Researcher notes

The bundle identifies the root cause and stable fix pattern, but omits CVSS, CWE, exploitability analysis, and distro package status. Validation should focus on driver reachability, kernel lineage, and whether downstream kernels have backported one of the referenced commits.

Mitigation direction

  • Update affected Linux kernels to versions containing the referenced stable fixes.
  • Prioritize systems using Kvaser USB CAN adapters or CAN bus workloads.
  • If immediate patching is unavailable, check vendor or distribution kernel advisories.
  • Disable or avoid loading kvaser_usb where the hardware is not needed.

Validation and detection

  • Inventory Linux hosts for Kvaser USB CAN hardware usage.
  • Check loaded modules for kvaser_usb on relevant systems.
  • Map running kernel versions against distribution advisories and stable fix commits.
  • Confirm patched kernels include the relevant kvaser_usb URB re-anchoring fix.
Prepared
Confidence
medium
Sources
9

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-23061 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
1ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux080f40a6fa28dab299da7a652e444b1e2d9231e7, 080f40a6fa28dab299da7a652e444b1e2d9231e7, 080f40a6fa28dab299da7a652e444b1e2d9231e7, 080f40a6fa28dab299da7a652e444b1e2d9231e7, 080f40a6fa28dab299da7a652e444b1e2d9231e7, 080f40a6fa28dab299da7a652e444b1e2d9231e7, 080f40a6fa28dab299da7a652e444b1e2d9231e7unaffected
LinuxLinux3.8, 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.