Analysis of AMDRyzenMasterDriver.sys: suspicious verdict, risk score 58/100. 2 YARA matches, 0/74 multi-engine detections. SHA256 0fd8b87d79828282. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver AMDRyzenMasterDriver.sys and assigned a verdict of Suspicious with a composite risk score of 58/100, indicating some risk signals warranting review (30-59 band).
| Verdict | Suspicious (58/100) |
| YARA matches | 2 |
| Multi-engine detections | 0 / 74 |
| File size | 60576 bytes |
| Code-signing signer | Advanced Micro Devices Inc. |
| Analyzed | 2026-08-15 |
| SHA256 | 0fd8b87d79828282a2b24c0680ecf6717c3bc284582af552ecea8d2e79c91b4b |
| SHA1 | 11c075264950dcb56cf373e2ab51ac8256df9e9e |
| MD5 | a9eee6b1c708789d0441d3d48c82f48f |
Version resource data embedded in the AMDRyzenMasterDriver.sys PE header, as extracted by the analysis engine.
| File description | AMD Ryzen Master Service Driver |
|---|---|
| Product | AMD Ryzen Master Service Driver |
| Company | Advanced Micro Devices |
| Original filename | AMDRyzenMasterDriver.sys |
| Internal name | AMDRyzenMasterDriver.sys |
| File version | 2.6.0.0 |
| Copyright | Copyright © 2024 AMD, Inc. |
Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.
| Component | Sub-score |
|---|---|
| Multi-engine consensus | 0 / 100 |
| YARA signature matches | 80 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 39 / 100 |
| Known-vulnerable corpus | 0 / 100 |
| Code-signing state | 80 / 100 |
| Packing and entropy | 0 / 100 |
| Dynamic behaviour | 0 / 100 |
| CVE cross-reference | 0 / 100 |
Kernel-mode APIs resolved from the Import Address Table of AMDRyzenMasterDriver.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapIoSpace | critical | Highly dangerous - potential for arbitrary code execution, memory corruption, or process termination |
| MmGetSystemRoutineAddress | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| HalGetBusDataByOffset | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| HalSetBusDataByOffset | high | Potentially dangerous - could be used for privilege escalation or security bypass |
| ZwSetValueKey | medium | Moderate risk - system modification capability |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| NtQuerySystemInformation | medium | Moderate risk - system modification capability |
| ObOpenObjectByPointer | medium | Moderate risk - system modification capability |
| ZwCreateKey | medium | Moderate risk - system modification capability |
| DbgPrintEx | low | Standard kernel API - generally benign |
| DbgPrint | low | Standard kernel API - generally benign |
| ZwClose | low | Standard kernel API - generally benign |
| KeDelayExecutionThread | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| IoCreateDeviceSecure | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| ZwQueryValueKey | low | Standard kernel API - generally benign |
Control codes reachable through the driver dispatch routine. Codes tied to published exploit code are flagged, since they are the primary Bring Your Own Vulnerable Driver (BYOVD) entry points.
| Code | Severity | Transfer | Description |
|---|---|---|---|
| 0x0080830F | high | METHOD_NEITHER | FILE_DEVICE_CUSTOM Function #195 |
| 0x00343D07 | high | METHOD_NEITHER | FILE_DEVICE_DISK Function #3905 |
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x00348BE8 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #762 |
| 0x00802484 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2337 |
| 0x00802494 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2341 |
| 0x00342444 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #2321 |
| 0x00340030 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #12 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0x008024B4 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2349 |
| 0x00340364 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #217 |
| 0x00340032 | medium | METHOD_OUT_DIRECT | FILE_DEVICE_DISK Function #12 |
| 0x00228368 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #218 |
Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.
| Section | Virtual size | Raw size | Entropy | Flags |
|---|---|---|---|---|
| .text | 0x5062 | 0x5200 | 5.8 | CODE, EXEC, READ |
| .rdata | 0x1120 | 0x1200 | 4.69 | IDATA, READ |
| .data | 0x20660 | 0x0400 | 2.32 | IDATA, READ, WRITE |
| .pdata | 0x039C | 0x0400 | 4.21 | IDATA, READ |
| PAGE | 0x1D0B | 0x1E00 | 6.17 | CODE, EXEC, READ |
| INIT | 0x0716 | 0x0800 | 4.76 | CODE, EXEC, READ, DISCARD |
| .rsrc | 0x03C8 | 0x0400 | 3.15 | IDATA, READ, DISCARD |
| .reloc | 0x0044 | 0x0200 | 0.87 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 85 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| BYOVD_MemRW | critical | Phys memory mapping + device creation |
| SUSP_PhysMem | high | Physical memory mapping |
Techniques this driver could enable if loaded by an adversary.
| ID | Technique | Tactic |
|---|---|---|
| T1003 | OS Credential Dumping | Credential Access |
| T1003.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| T1006 | Direct Volume Access | Defense Evasion |
| T1014 | Rootkit | Defense Evasion |
| T1055.012 | Process Hollowing | Defense Evasion |
| T1068 | Exploitation for Privilege Escalation | Privilege Escalation |
| T1071 | Application Layer Protocol | Command and Control |
| T1112 | Modify Registry | Defense Evasion |
| T1211 | Exploitation for Defense Evasion | Defense Evasion |
| T1542.001 | Pre-OS Boot: System Firmware | Persistence |
| T1543.003 | Windows Service | Persistence |
| T1547.001 | Registry Run Keys | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1601 | Modify System Image | Defense Evasion |
| T1652 | Device Driver Discovery | Discovery |
| Signer | Advanced Micro Devices Inc. |
|---|---|
| Signer organisation | Advanced Micro Devices Inc. |
| Issuer | Sectigo RSA Code Signing CA |
| Serial | 535091E6CAB13AF393B51EAD0825F627 |
| Valid from | 2021-05-11 00:00 UTC |
| Valid until | 2024-05-10 23:59 UTC (expired) |
| Signature validity | Not verified |
Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. Exploitable paths: 1.
Based on DriverShield static and dynamic analysis, AMDRyzenMasterDriver.sys shows some suspicious signals and warrants manual review. Its composite risk score is 58/100 (verdict: suspicious). Always validate findings independently before acting.
AMDRyzenMasterDriver.sys has a DriverShield composite risk score of 58/100, placing it in the suspicious verdict band. SHA256: 0fd8b87d79828282a2b24c0680ecf6717c3bc284582af552ecea8d2e79c91b4b.
AMDRyzenMasterDriver.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Advanced Micro Devices Inc..
Related: Other drivers signed by Advanced Micro Devices Inc. · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas