# CVE-2025-6217: PEAK-System Driver PCANFD_ADD_FILTERS Time-Of-Check Time-Of-Use Information Disclosure Vulnerability

> Local attackers can exploit a race condition in the PCANFD_ADD_FILTERS IOCTL to disclose sensitive information and potentially execute kernel code.

- **Severity:** Low 3.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-cfhg-h373-g4mj

## What is CVE-2025-6217?

CVE-2025-6217 is a low-severity vulnerability in PEAK-System Driver, published on 21 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2025-6217?

It affects 1 product.


Products: Peak-System Device Driver.

## How do I fix CVE-2025-6217?

No fix has been published for CVE-2025-6217 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6217 being exploited?

There is no known exploitation of CVE-2025-6217 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6217 and fix it if it is affected.

What it is: CVE-2025-6217 is a low-severity vulnerability in PEAK-System Driver, published on 21 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6217 in the wild and no public exploit code.

Affected product: PEAK-System Driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6217/ (Markdown: https://insights.sbomify.com/CVE-2025-6217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6217
- OSV: https://osv.dev/vulnerability/CVE-2025-6217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6217/
Summaries are generated and may contain mistakes; the official description above is the record.