# CVE-2025-52915: Privilege escalation in n/a

> An admin-privileged user can exploit insufficient caller validation in the K7 Security driver to terminate protected processes, causing denial of service.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-fw9m-856v-56h4

## What is CVE-2025-52915?

CVE-2025-52915 is a high-severity vulnerability in n/a, published on 9 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

K7RKScan.sys 23.0.0.10, part of the K7 Security Anti-Malware suite, allows an admin-privileged user to send crafted IOCTL requests to terminate processes that are protected through a third-party implementation. This is caused by insufficient caller validation in the driver's IOCTL handler, enabling unauthorized processes to perform those actions in kernel space. Successful exploitation can lead to denial of service by disrupting critical third-party services or applications.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-52915 being exploited?

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

Public exploit code:

- BYOVD research use cases featuring vulnerable driver discovery and reverse engineering methodology.  (CVE-2025-52915,  CVE-2025-1055, CVE-2026-3609, CVE-2026-8501). (github_poc): https://github.com/BlackSnufkin/BYOVD

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52915 is a high-severity vulnerability in n/a, published on 9 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52915 in the wild and no public exploit code.

Affected product: n/a. 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-52915/ (Markdown: https://insights.sbomify.com/CVE-2025-52915/index.md)
```

## Sources

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

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