Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-110322 Overview
CVE-2026-110322 affects the PEAK-System PCAN driver processing path for type 0x4030 requests. The driver fails to validate a selected or returned object pointer before dereferencing fixed fields during post-processing. A local, authenticated attacker can trigger the untrusted pointer dereference and crash the affected component. The flaw maps to [CWE-822: Untrusted Pointer Dereference] and impacts availability only. The vulnerability was published through CISA ICS Advisory ICSA-26-293-01.
Critical Impact
Local authenticated users can trigger an untrusted pointer dereference in the PEAK-System PCAN type 0x4030 handler, producing a denial-of-service condition against the affected driver component.
Affected Products
- PEAK-System PCAN driver (type 0x4030 processing path)
- Industrial control system integrations referenced in CISA advisory ICSA-26-293-01
- HMS Networks products referenced in the advisory bundle
Discovery Timeline
- 2026-10-20 - CVE-2026-110322 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-110322
Vulnerability Analysis
The PEAK-System PCAN driver exposes an input/output control (IOCTL) interface that dispatches requests to internal handlers based on a type value. When the driver processes a request of type 0x4030, it selects or returns an object pointer that participates in subsequent post-processing. The driver dereferences fixed fields on that pointer without first confirming the pointer refers to a valid, driver-owned object.
An attacker with local access and low privileges can influence the selection logic so the post-processing routine operates on an invalid or attacker-chosen pointer. Dereferencing the fixed fields on that pointer causes memory access violations in kernel or driver context. The weakness is classified as [CWE-822: Untrusted Pointer Dereference].
The impact is limited to availability. The vulnerability does not expose confidentiality or integrity of data, but repeated exploitation can render the CAN interface or host unusable until restart.
Root Cause
The root cause is missing validation between pointer selection and pointer use. The handler for type 0x4030 assumes the object pointer returned by an earlier selection step is well-formed and owned by the driver. No sanity check, allocation tag check, or object-table lookup gates the dereference.
Attack Vector
Exploitation requires local access and valid credentials sufficient to open the PCAN device and issue IOCTLs. No user interaction is required. An attacker sends a crafted request of type 0x4030 to drive the handler into a state where post-processing dereferences an untrusted pointer. The result is a crash of the driver or host, denying service to any process relying on the CAN interface. Verified exploitation code is not available in public sources at this time. See the CISA ICS Advisory ICSA-26-293-01 and the GitHub CSAF file for authoritative technical details.
Detection Methods for CVE-2026-110322
Indicators of Compromise
- Unexpected crashes, bugchecks, or kernel panics referencing the PEAK-System PCAN driver module.
- System or application event log entries recording faults in the PCAN device driver shortly after local IOCTL activity.
- Loss of CAN bus connectivity on hosts where the PCAN driver was previously stable.
Detection Strategies
- Monitor process creation and handle opens targeting PCAN device objects by non-administrative users.
- Correlate driver crash telemetry with preceding IOCTL activity from local user sessions.
- Alert on repeated service or driver restarts associated with the PEAK-System PCAN stack.
Monitoring Recommendations
- Centralize Windows kernel crash dumps and driver fault logs for review against this CVE.
- Track inventory of hosts running the PEAK-System PCAN driver, particularly engineering workstations connected to industrial control systems.
- Review access to CAN interface devices and restrict interactive logon to those hosts.
How to Mitigate CVE-2026-110322
Immediate Actions Required
- Identify all hosts running the PEAK-System PCAN driver and verify installed versions against vendor advisories.
- Restrict local, interactive access on engineering workstations and operator consoles that expose the PCAN device.
- Apply least privilege for accounts allowed to open the PCAN device and issue IOCTLs.
Patch Information
Consult the vendor for fixed driver versions. Updated software is distributed through the Peak-System software downloads page. Additional guidance for related products is available on the HMS Networks cybersecurity resource page. Follow the remediation steps in CISA ICS Advisory ICSA-26-293-01 until a verified patched version is deployed.
Workarounds
- Disable or unload the PEAK-System PCAN driver on hosts that do not require CAN connectivity.
- Segment affected hosts on isolated OT networks and block remote interactive access.
- Enforce application allowlisting to prevent untrusted local binaries from issuing IOCTLs to the PCAN device.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

