CVE-2025-6217VulnerabilityPublished 21 Jun 2025Updated 23 Jun 2025

CVE-2025-6217: PEAK-System Driver · Time-of-check Time-of-use (TOCTOU) Race Condition

Affects PEAK-System DriverSource CVE Database V5

Not known to be exploited · CVSS 3.8 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

3.8Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PEAK-System Driver	Affected =8.18.0	Fixed in–

AI-suggested

1. Restrict local access: Limit the ability to execute low-privileged code locally by enforcing strict endpoint security controls, including application whitelisting and robust user privilege management. 2. Monitor and audit: Implement detailed logging and monitoring of driver-related IOCTL calls and unusual local process behaviors to detect potential exploitation attempts early. 3. Segmentation: Isolate systems running PEAK-System drivers, especially those interfacing with critical industrial or automotive networks, to reduce the attack surface and prevent lateral movement. 4. Update and patch management: Although no patches are currently linked, maintain close communication with PEAK-System for timely updates and apply patches immediately upon release. 5. Code integrity checks: Employ kernel-mode code signing enforcement and integrity verification to prevent unauthorized or malicious driver modifications. 6. Defense in depth: Combine this with network-level protections and endpoint detection and response (EDR) solutions that can identify suspicious local activities indicative of exploitation attempts. 7. Vulnerability chaining awareness: Train security teams to recognize that this vulnerability can be part of a multi-stage attack and to prioritize investigation of related anomalies that could indicate privilege escalation attempts.

Description

PEAK-System Driver PCANFD_ADD_FILTERS Time-Of-Check Time-Of-Use Information Disclosure Vulnerability. This vulnerability allows local attackers to disclose sensitive information on affected installations of PEAK-System Driver. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the handling of the PCANFD_ADD_FILTERS IOCTL. The issue results from the lack of proper locking when performing operations on an object. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the kernel. Was ZDI-CAN-24161.

Impact

For European organizations, the primary impact of CVE-2025-6217 lies in the potential exposure of sensitive information on systems running the affected PEAK-System Driver version 8.18.0. Since the vulnerability requires local low-privileged code execution, it is most relevant in environments where attackers can gain initial access, such as through phishing, insider threats, or other local attack vectors. The driver is commonly used in automotive diagnostics, industrial automation, and embedded systems, sectors that are significant in Europe’s manufacturing and automotive industries. Disclosure of sensitive information could include configuration details, memory contents, or other data that might facilitate further exploitation or lateral movement. If chained with other vulnerabilities, attackers could escalate privileges to kernel level, leading to full system compromise. This could disrupt critical infrastructure, manufacturing processes, or automotive systems, potentially causing operational downtime or safety risks. The low CVSS score does not fully capture the risk of chained exploits or the strategic importance of affected systems in European industrial environments. Organizations relying on PEAK-System hardware and drivers should be aware of this vulnerability’s potential to serve as an initial step in sophisticated attack campaigns targeting industrial control systems or automotive technology.

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Implementation
The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
Implementation
When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Architecture and Design
Limit the interleaving of operations on files from multiple processes.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.3 (opens in a new tab)
V11.1.6 (opens in a new tab)
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-25-408/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jun 2025, 12:52 UTC

WeaknessesCWE-367

Technical details

References

Community reviews

Related threats