LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23347: can: usb: f81604: correctly anchor the urb in the read bulk callback

In the Linux kernel, the following vulnerability has been resolved: can: usb: f81604: correctly anchor the urb in the read bulk callback When submitting an urb, that is using the anchor pattern, it needs to be anchored before submitting it otherwise it could be leaked if usb_kill_anchored_urbs() is called. This logic is correctly done elsewhere in the driver, except in the read bulk callback so do that here also.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects a USB CAN driver. A driver bookkeeping error can leave a submitted USB request untracked, so cleanup may miss it and leak resources. The public record does not provide CVSS, confirmed impact beyond the leak condition, or evidence of active exploitation.

Executive priority

Treat as a targeted kernel maintenance item unless your environment uses USB CAN hardware or custom kernels. Prioritize affected operational technology, lab, automotive, or embedded systems where CAN USB adapters are present.

Technical view

In the Linux kernel f81604 USB CAN driver, the read bulk callback submitted a URB before anchoring it. If usb_kill_anchored_urbs() runs, that URB may not be killed and can be leaked. Kernel stable commits correct the anchor-before-submit ordering.

Likely exposure

Exposure appears limited to Linux systems using, loading, or shipping the f81604 USB CAN driver. The bundle lists Linux kernel versions and stable commits, but does not provide distro package names, CPEs, or a precise deployment profile.

Exploitation context

The CVE bundle marks KEV as false and provides no cited evidence of exploitation. The described condition is a driver resource-leak scenario tied to USB CAN driver cleanup behavior, not a publicly documented remote attack path.

Researcher notes

Key evidence is limited to the CVE description and Linux stable commit references. No CWE, CVSS, exploit maturity, distro package mapping, or concrete attacker prerequisites are provided in the supplied sources.

Mitigation direction

  • Apply a vendor or distribution kernel update containing the referenced stable fix.
  • Confirm whether f81604 USB CAN driver support is present in deployed kernels.
  • Track Linux stable commits listed for this CVE if maintaining custom kernels.
  • Use vendor guidance before applying any temporary driver configuration workaround.

Validation and detection

  • Inventory Linux kernel versions across systems that use CAN USB hardware.
  • Check whether the f81604 driver is built, loadable, or actively loaded.
  • Verify installed kernel packages include the referenced stable fix or downstream backport.
  • Review vendor advisories for distro-specific fixed package versions.
Prepared
Confidence
medium
Sources
7

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-23347 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
6Source 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
LinuxLinux88da17436973e463bed59bea79771fb03a21555e, 88da17436973e463bed59bea79771fb03a21555e, 88da17436973e463bed59bea79771fb03a21555e, 88da17436973e463bed59bea79771fb03a21555e, 88da17436973e463bed59bea79771fb03a21555eunaffected
LinuxLinux6.5, 0, 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.