LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23031: can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak

In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak In gs_can_open(), the URBs for USB-in transfers are allocated, added to the parent->rx_submitted anchor and submitted. In the complete callback gs_usb_receive_bulk_callback(), the URB is processed and resubmitted. In gs_can_close() the URBs are freed by calling usb_kill_anchored_urbs(parent->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 gs_can_close(). Fix the memory leak by anchoring the URB in the gs_usb_receive_bulk_callback() to the parent->rx_submitted anchor.

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-23031 is a Linux kernel memory leak in the gs_usb CAN-over-USB driver. Systems using affected kernels and gs_usb-compatible USB CAN adapters may leak kernel memory during device receive handling and close operations. No CVSS score or exploitation evidence is provided in the bundle.

Executive priority

Treat this as a targeted reliability risk, not a broad emergency. Prioritize operational technology, embedded Linux, and systems with USB CAN interfaces, then fold remediation into the next kernel maintenance cycle unless vendor guidance raises urgency.

Technical view

The gs_usb receive bulk completion path loses URB ownership because USB unanchors the URB before the completion callback runs. gs_can_close() later kills only anchored URBs, so completed receive URBs can escape cleanup. Stable kernel commits re-anchor the URB in gs_usb_receive_bulk_callback().

Likely exposure

Exposure is most likely on Linux systems, appliances, or industrial/embedded environments that load the gs_usb driver for USB CAN interfaces. General-purpose Linux hosts without this driver or hardware path are less likely exposed.

Exploitation context

The bundle does not show active exploitation, KEV listing, public exploit details, or a CVSS score. The described impact is a kernel memory leak, so the main concern is reliability or resource exhaustion where affected hardware and driver paths are reachable.

Researcher notes

Evidence supports a gs_usb URB lifecycle bug fixed in Linux stable commits. The source bundle does not provide CVSS, CWE, proof-of-concept status, or detailed Siemens product impact, so validation should stay source-driven and product-specific.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize systems using USB CAN adapters or gs_usb-loaded kernels.
  • Review Siemens ProductCERT guidance for product-specific exposure.
  • If updates are unavailable, follow vendor guidance for temporary mitigations.

Validation and detection

  • Inventory Linux kernel versions against the affected version data.
  • Check whether the gs_usb driver is present or loaded.
  • Identify systems using USB CAN hardware in production.
  • Confirm installed kernel includes one of the referenced stable fixes.
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-23031 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

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

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd08e973a77d128b25e01a08c34d89593fdf222da, d08e973a77d128b25e01a08c34d89593fdf222da, d08e973a77d128b25e01a08c34d89593fdf222da, d08e973a77d128b25e01a08c34d89593fdf222da, d08e973a77d128b25e01a08c34d89593fdf222da, d08e973a77d128b25e01a08c34d89593fdf222daunaffected
LinuxLinux3.16, 0, 5.15.203, 6.1.162, 6.6.122, 6.12.67, 6.18.7, 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.