CVE-2025-51060: An issue was discovered in CPUID cpuz.sys 1.0.5.4.
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.
Security readout for executives and security teams
Plain-English summary
CVE-2025-51060 concerns CPUID’s cpuz.sys driver version 1.0.5.4. The driver may allow unsafe low-level CPU register access that can help an attacker execute code in kernel context on some 64-bit Windows systems. Business urgency is moderate unless this driver is widely deployed or loaded on sensitive endpoints.
Executive priority
Prioritize assessment on privileged workstations, developer systems, and servers that allow third-party driver installation. Treat as a moderate endpoint hardening issue unless inventory shows broad deployment or sensitive-system exposure.
Technical view
The issue is improper access control in cpuz.sys 1.0.5.4. The CVE describes unvalidated DeviceIoControl handling enabling RDMSR and WRMSR, which can alter MSR_LSTAR and support kernel-context execution when Windows core isolation is absent or disabled. 32-bit Windows impact is unconfirmed.
Likely exposure
Exposure is likely limited to Windows systems where CPUID cpuz.sys 1.0.5.4 is present and loadable. The source notes successful operation on 64-bit Windows when core isolation is absent or disabled. The CVE record does not provide complete affected product metadata.
Exploitation context
No CISA KEV listing or cited source confirms active exploitation. The public reference appears technical and driver-focused. The CVSS vector lists network attack characteristics, but the described abuse involves a Windows kernel driver interface, so defenders should validate real-world access requirements in their environment.
Researcher notes
Evidence is limited to the CVE record and the referenced GitHub repository. The affected vendor/product fields are incomplete in the CVE data. Avoid relying solely on the CVSS vector; validate local driver accessibility, Windows architecture, and core isolation status.
Mitigation direction
Inventory systems for cpuz.sys version 1.0.5.4.
Remove or disable the driver where it is not required.
Check CPUID or vendor guidance for updates or replacement drivers.
Enable Windows core isolation where compatible and operationally safe.
Restrict installation and loading of unnecessary third-party kernel drivers.
Validation and detection
Search endpoint inventories for cpuz.sys and record file versions.
Confirm whether the driver is currently loaded on Windows endpoints.
Review Windows core isolation status on affected systems.
Check EDR or driver telemetry for unexpected cpuz.sys loading.
Track vendor advisories for a confirmed fixed version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.