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

> An attacker can escalate privileges to kernel mode by exploiting unvalidated DeviceIoControl parameters in the CPUID cpuz.sys driver to execute arbitrary code.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-g7m4-99vh-h98v

## What is CVE-2025-51060?

CVE-2025-51060 is a medium-severity vulnerability in n/a, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in CPUID cpuz.sys 1.0.5.4. An attacker can use DeviceIoControl with the unvalidated parameters 0x9C402440 and 0x9C402444 as IoControlCodes to perform RDMSR and WRMSR, respectively. Through this process, the attacker can modify MSR_LSTAR and hook KiSystemCall64. Afterward, using Return-Oriented Programming (ROP), the attacker can manipulate the stack with pre-prepared gadgets, disable the SMAP flag in the CR4 register, and execute a user-mode syscall handler in the kernel context. It has not been confirmed whether this works on 32-bit Windows, but it functions on 64-bit Windows if the core isolation feature is either absent or disabled.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Cpuid Cpuz.sys.

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

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

## Is CVE-2025-51060 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51060 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51060 is a medium-severity vulnerability in n/a, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51060 exists.

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-51060/ (Markdown: https://insights.sbomify.com/CVE-2025-51060/index.md)
```

## Sources

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

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