Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Cpuid | Cpu-z | — |
| Microsoft | Windows | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-23645 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.330% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/ZiaLib/Zmsr |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Cpuid cpuz.sys
|
|
| CPEs | cpe:2.3:a:cpuid:cpuz.sys:1.0.5.4:*:*:*:*:windows:*:* | |
| Vendors & Products |
Cpuid cpuz.sys
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Cpuid
Cpuid cpu-z Microsoft Microsoft windows |
|
| Vendors & Products |
Cpuid
Cpuid cpu-z Microsoft Microsoft windows |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-284 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| References |
|