Analysis of rtkiow10x64.sys: vulnerable verdict, risk score 72/100. 3 YARA matches, 1/75 multi-engine detections. SHA256 32e1a8513eee746d. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.
DriverShield analyzed the Windows kernel driver rtkiow10x64.sys and assigned a verdict of Vulnerable with a composite risk score of 72/100, indicating a known or likely vulnerability surface (60-79 band).
| Verdict | Vulnerable (72/100) |
| YARA matches | 3 |
| Multi-engine detections | 1 / 75 |
| File size | 56304 bytes |
| Code-signing signer | DigiCert High Assurance EV Root CA |
| Analyzed | 2026-09-06 |
| SHA256 | 32e1a8513eee746d17eb5402fb9d8ff9507fb6e1238e7ff06f7a5c50ff3df993 |
| SHA1 | 947db58d6f36a8df9fa2a1057f3a7f653ccbc42e |
| MD5 | b5ada7fd226d20ec6634fc24768f9e22 |
Version resource data embedded in the rtkiow10x64.sys PE header, as extracted by the analysis engine.
| File description | Realtek IO Driver |
|---|---|
| Product | Realtek IO Driver |
| Company | Realtek |
| Original filename | rtkiow10x64.sys |
| Internal name | rtkiow10x64.sys |
| File version | 1.008.0823.2017 |
| Copyright | Copyright (C) 2017 Realtek Semiconductor Corporation. All Right Reserved. |
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 | 85 / 100 |
| Dangerous kernel imports | 100 / 100 |
| IOCTL dispatch surface | 36 / 100 |
| Known-vulnerable corpus | 100 / 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 rtkiow10x64.sys, ranked by exploitation relevance.
| API | Risk | Why it matters |
|---|---|---|
| MmMapLockedPagesSpecifyCache | 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 |
| MmUnmapIoSpace | medium | Moderate risk - system modification capability |
| ZwClose | low | Standard kernel API - generally benign |
| RtlInitUnicodeString | low | Standard kernel API - generally benign |
| IoCreateDevice | low | Standard kernel API - generally benign |
| IoDeleteSymbolicLink | low | Standard kernel API - generally benign |
| IoDeleteDevice | low | Standard kernel API - generally benign |
| IofCompleteRequest | low | Standard kernel API - generally benign |
| ZwOpenKey | low | Standard kernel API - generally benign |
| ExAllocatePoolWithTag | low | Standard kernel API - generally benign |
| ZwQueryValueKey | low | Standard kernel API - generally benign |
| IoCreateSymbolicLink | 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 |
|---|---|---|---|
| 0x002200F0 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #60 |
| 0x008024BC | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2351 |
| 0x00802484 | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2337 |
| 0x0080248C | medium | METHOD_BUFFERED | FILE_DEVICE_CUSTOM Function #2339 |
| 0xC350B800 | medium | METHOD_BUFFERED | CUSTOM_MSI Function #3584 |
| 0x0034EF05 | medium | METHOD_IN_DIRECT | FILE_DEVICE_DISK Function #3009 |
| 0x0080EC81 | medium | METHOD_IN_DIRECT | FILE_DEVICE_CUSTOM Function #2848 |
| 0x0022E840 | medium | METHOD_BUFFERED | FILE_DEVICE_UNKNOWN Function #2576 |
| 0x0022F045 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #3089 |
| 0x0022B941 | medium | METHOD_IN_DIRECT | FILE_DEVICE_UNKNOWN Function #3664 |
| 0x00340404 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #257 |
| 0x00340088 | medium | METHOD_BUFFERED | FILE_DEVICE_DISK Function #34 |
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 | 0x423B | 0x4400 | 6.26 | CODE, EXEC, READ |
| .rdata | 0x08D4 | 0x0A00 | 4.25 | IDATA, READ |
| .data | 0x0100 | 0x0200 | 0.34 | IDATA, READ, WRITE |
| .pdata | 0x0294 | 0x0400 | 2.95 | IDATA, READ |
| PAGE | 0x06B4 | 0x0800 | 5.44 | CODE, EXEC, READ |
| INIT | 0x0720 | 0x0800 | 5.35 | CODE, EXEC, READ, DISCARD |
| .rsrc | 0x0468 | 0x0600 | 2.58 | IDATA, READ, DISCARD |
| .reloc | 0x0024 | 0x0200 | 0.4 | IDATA, READ, DISCARD |
| Control Flow Guard | Enabled |
|---|---|
| ASLR | Enabled |
| DEP | Enabled |
| Integrity check | Not enforced |
| Mitigation score | 85 / 100 |
| Rule | Severity | Detects |
|---|---|---|
| PUA_VULN_Driver_Realtek_Rtkiowxsys_Realtekiodriver_32E1 | medium | Detects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - rtkio.sys, rtkio64.sys, rtkiow8x64.sys, rtkiow10x64.sys. Investigate matches... |
| 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.001 | OS Credential Dumping: LSASS Memory | Credential Access |
| 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 |
| T1543.003 | Windows Service | Persistence |
| T1547.001 | Registry Run Keys | Persistence |
| T1553.002 | Subvert Trust Controls: Code Signing | Defense Evasion |
| T1562.001 | Impair Defenses | Defense Evasion |
| T1569.002 | Service Execution | Execution |
| T1652 | Device Driver Discovery | Discovery |
| Signer | DigiCert High Assurance EV Root CA |
|---|---|
| Signer organisation | DigiCert Inc |
| Issuer | Microsoft Code Verification Root |
| Serial | 61204DB4000000000027 |
| Valid from | 2011-04-15 19:45 UTC |
| Valid until | 2021-04-15 19:55 UTC (expired) |
| Signature validity | Not verified |
Engine angr, status completed, 56 paths explored at a maximum depth of 56. Vulnerability classes reached: 1. Exploitable paths: 1.
Corpus match: this hash is present in the known-vulnerable driver corpus DriverShield cross-references during analysis, which is why the score carries a full weighting on that component.
Based on DriverShield static and dynamic analysis, rtkiow10x64.sys is flagged as vulnerable and is a potential Bring Your Own Vulnerable Driver (BYOVD) risk. Its composite risk score is 72/100 (verdict: vulnerable). Always validate findings independently before acting.
rtkiow10x64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: 32e1a8513eee746d17eb5402fb9d8ff9507fb6e1238e7ff06f7a5c50ff3df993.
rtkiow10x64.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by DigiCert High Assurance EV Root CA.
Related: Other drivers signed by DigiCert High Assurance EV Root CA · What an IOCTL dispatch code is · How YARA matching feeds the score · BYOVD research index · full driver database · CVE library · code signing atlas