LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23082: can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error

In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error In commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak"), the URB was re-anchored before usb_submit_urb() in gs_usb_receive_bulk_callback() to prevent a leak of this URB during cleanup. However, this patch did not take into account that usb_submit_urb() could fail. The URB remains anchored and usb_kill_anchored_urbs(&parent->rx_submitted) in gs_can_close() loops infinitely since the anchor list never becomes empty. To fix the bug, unanchor the URB when an usb_submit_urb() error occurs, also print an info message.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver reliability flaw in the gs_usb CAN USB path. If a USB request resubmission fails, cleanup can loop forever when the CAN interface closes. The documented impact is a hang or denial of service, not data theft or remote code execution.

Executive priority

Treat as targeted operational risk for Linux systems supporting CAN/industrial or embedded workflows. Prioritize patching where gs_usb CAN adapters are used; broader enterprise urgency is lower without evidence of exploitation or network reachability.

Technical view

In gs_usb_receive_bulk_callback(), an URB is re-anchored before usb_submit_urb(). If submission fails, the URB remains anchored, causing usb_kill_anchored_urbs(&parent->rx_submitted) in gs_can_close() to loop indefinitely. The fix unanchors the URB on usb_submit_urb() error and logs an informational message.

Likely exposure

Exposure appears limited to Linux systems using the gs_usb CAN USB driver, especially hosts connected to gs_usb-compatible CAN adapters. General Linux servers without this driver or hardware path are unlikely to be affected based on the provided sources.

Exploitation context

No active exploitation is cited, and the CVE is not marked KEV. The sources describe a kernel cleanup hang triggered by an error path, but do not provide evidence of remote exploitation or privilege escalation.

Researcher notes

The evidence names no CVSS, CWE, or exploit status. Analysis should focus on affected kernel lineage, presence of the gs_usb driver, and whether the fix commits are included in vendor kernels. Avoid assuming broader CAN stack impact.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fix.
  • Confirm distro backports rather than relying only on upstream version numbers.
  • Prioritize systems using gs_usb CAN USB adapters.
  • If patch timing is unclear, check vendor guidance for supported mitigations.

Validation and detection

  • Inventory systems loading the gs_usb kernel driver.
  • Identify hosts with USB CAN hardware using this driver path.
  • Verify the running kernel includes the upstream stable fix or vendor backport.
  • Review operational reports for CAN interface close hangs after USB errors.
Prepared
Confidence
medium
Sources
8

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-23082 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
7Source 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
LinuxLinux9c151898cc259a7784be60ba38664f42ede39b31, ec5ccc2af9e5b045671f3f604b57512feda8bcc5, f905bcfa971edb89e398c98957838d8c6381c0c7, 08624b7206ddb9148eeffc2384ebda2c47b6d1e9, 9f669a38ca70839229b7ba0f851820850a2fe1f7, 7352e1d5932a0e777e39fa4b619801191f57e603unaffected
LinuxLinux6.12.67, 6.18.7unaffected
Weakness

CWE details

No CWE listed

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