LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23298: can: ucan: Fix infinite loop from zero-length messages

In the Linux kernel, the following vulnerability has been resolved: can: ucan: Fix infinite loop from zero-length messages If a broken ucan device gets a message with the message length field set to 0, then the driver will loop for forever in ucan_read_bulk_callback(), hanging the system. If the length is 0, just skip the message and go on to the next one. This has been fixed in the kvaser_usb driver in the past in commit 0c73772cd2b8 ("can: kvaser_usb: leaf: Fix potential infinite loop in command parsers"), so there must be some broken devices out there like this somewhere.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23298 is a Linux kernel availability issue in the ucan USB CAN driver. A malformed zero-length device message can trap the driver in an endless loop and hang the system. The main business risk is local operational disruption on systems using affected CAN hardware, not confirmed remote compromise.

Executive priority

Treat as a targeted availability risk. Patch during the next maintenance window for general fleets, but accelerate for industrial, automotive, or lab systems depending on USB CAN reliability needs.

Technical view

The ucan driver’s bulk read callback can loop forever when a received message has length 0. Linux resolved this by skipping zero-length messages and continuing parsing. The CVE lists Linux as affected across several maintained kernel lines and provides stable kernel fix commits.

Likely exposure

Exposure appears limited to Linux systems that use the affected ucan CAN driver with compatible USB CAN devices. General servers without this driver or hardware are unlikely to be exposed based on the provided sources.

Exploitation context

The source describes a broken ucan device causing the condition. There is no KEV listing and no provided evidence of active exploitation, public weaponization, or remote attack paths.

Researcher notes

The record lacks CVSS, CWE, and detailed attack preconditions. Analysis should avoid assuming remote reachability. Key validation is whether ucan is present, loaded, and connected to devices capable of producing zero-length messages.

Mitigation direction

  • Apply the relevant Linux stable kernel update containing the ucan fix.
  • Check your Linux distribution’s kernel advisory for backported fixes.
  • Prioritize systems using USB CAN hardware or the ucan driver.
  • Remove exposure to untrusted or faulty ucan devices until patched, if operationally feasible.

Validation and detection

  • Inventory Linux hosts for kernel versions listed as affected in the CVE record.
  • Identify systems using CAN USB hardware or loading the ucan driver.
  • Confirm vendor kernel packages include one of the referenced stable fixes or a backport.
  • Review affected operational systems for unexplained hangs around CAN device activity.
Prepared
Confidence
medium
Sources
10

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-23298 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
9Source 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
LinuxLinux9f2d3eae88d26c29d96e42983b755940d9169cd9, 9f2d3eae88d26c29d96e42983b755940d9169cd9, 9f2d3eae88d26c29d96e42983b755940d9169cd9, 9f2d3eae88d26c29d96e42983b755940d9169cd9, 9f2d3eae88d26c29d96e42983b755940d9169cd9, 9f2d3eae88d26c29d96e42983b755940d9169cd9, 9f2d3eae88d26c29d96e42983b755940d9169cd9, 9f2d3eae88d26c29d96e42983b755940d9169cd9unaffected
LinuxLinux4.19, 0, 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.77, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

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