rtkiow8x64.sys - Vulnerable (72/100) - DriverShield Analysis

Analysis of rtkiow8x64.sys: vulnerable verdict, risk score 72/100. 3 YARA matches, 0/75 multi-engine detections. SHA256 b205835b818d8a50. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

rtkiow8x64.sys - Analysis Report

DriverShield analyzed the Windows kernel driver rtkiow8x64.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).

VerdictVulnerable (72/100)
YARA matches3
Multi-engine detections0 / 75
File size55984 bytes
Code-signing signerDigiCert High Assurance EV Root CA
Analyzed2026-09-06
SHA256b205835b818d8a50903cf76936fcf8160060762725bd74a523320cfbd091c038
SHA198ceed786f79288becc08c3b82c57e8d4bfa1bca
MD5480f2ca1679056019dbc8abece3fa3cb

Driver identity

Version resource data embedded in the rtkiow8x64.sys PE header, as extracted by the analysis engine.

File descriptionRealtek IO Driver
ProductRealtek IO Driver
CompanyRealtek
Original filenamertkiow8x64.sys
Internal namertkiow8x64.sys
File version1.009.0709.2020
CopyrightCopyright (C) 2020 Realtek Semiconductor Corporation. All Right Reserved.

How the 72/100 score breaks down

Each component is scored 0-100 and then weighted into the composite. See the analysis methodology for the exact formula.

ComponentSub-score
Multi-engine consensus0 / 100
YARA signature matches85 / 100
Dangerous kernel imports100 / 100
IOCTL dispatch surface60 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (18)

Kernel-mode APIs resolved from the Import Address Table of rtkiow8x64.sys, ranked by exploitation relevance.

APIRiskWhy it matters
MmMapIoSpacecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmMapLockedPagesSpecifyCachecriticalHighly dangerous - potential for arbitrary code execution, memory corruption, or process termination
MmGetSystemRoutineAddresshighPotentially dangerous - could be used for privilege escalation or security bypass
ObOpenObjectByPointermediumModerate risk - system modification capability
ZwCreateKeymediumModerate risk - system modification capability
MmUnmapIoSpacemediumModerate risk - system modification capability
ZwSetValueKeymediumModerate risk - system modification capability
ZwCloselowStandard kernel API - generally benign
IoCreateSymbolicLinklowStandard kernel API - generally benign
RtlInitUnicodeStringlowStandard kernel API - generally benign
IoCreateDevicelowStandard kernel API - generally benign
IoDeleteDevicelowStandard kernel API - generally benign
ZwQueryValueKeylowStandard kernel API - generally benign
ZwOpenKeylowStandard kernel API - generally benign
ExAllocatePoolWithTaglowStandard kernel API - generally benign
IofCompleteRequestlowStandard kernel API - generally benign
IoDeleteSymbolicLinklowStandard kernel API - generally benign
IoCreateDeviceSecurelowStandard kernel API - generally benign

IOCTL dispatch codes (20)

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.

CodeSeverityTransferDescription
0x00343D07highMETHOD_NEITHERFILE_DEVICE_DISK Function #3905
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x008024BCmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2351
0xC350B800mediumMETHOD_BUFFEREDCUSTOM_MSI Function #3584
0x0034FF0DmediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #4035
0x00348005mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1
0x0034D815mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1541
0x00345305mediumMETHOD_IN_DIRECTFILE_DEVICE_DISK Function #1217
0x0080EC81mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #2848
0x00220020mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #8
0x0080C481mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #288
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x0022E840mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #2576
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x0022EF45mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #3025
0x003403FCmediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #255
0x00340088mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #34
0x00340036mediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #13

PE sections

Section layout and Shannon entropy. High entropy in a code section is a packing or encryption indicator.

SectionVirtual sizeRaw sizeEntropyFlags
.text0x3EFB0x40006.38CODE, EXEC, READ
.rdata0x0EE40x10004.4IDATA, READ
.data0x03080x04001.27IDATA, READ, WRITE
.pdata0x03D80x04004.21IDATA, READ
PAGE0x22240x24006.1CODE, EXEC, READ
INIT0x0A700x0C005.22CODE, EXEC, READ, DISCARD
.rsrc0x04600x06002.58IDATA, READ, DISCARD
.reloc0x00300x02000.57IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardEnabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score85 / 100

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Realtek_Rtkiowxsys_Realtekiodriver_B205mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - rtkiow8x64.sys . Investigate matches in context: expected filenames or stand...
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (14)

Techniques this driver could enable if loaded by an adversary.

IDTechniqueTactic
T1003OS Credential DumpingCredential Access
T1003.001OS Credential Dumping: LSASS MemoryCredential Access
T1006Direct Volume AccessDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerDigiCert High Assurance EV Root CA
Signer organisationDigiCert Inc
IssuerMicrosoft Code Verification Root
Serial61204DB4000000000027
Valid from2011-04-15 19:45 UTC
Valid until2021-04-15 19:55 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status completed, 100 paths explored at a maximum depth of 100. Vulnerability classes reached: 0. Exploitable paths: 2.

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.

Frequently asked questions about rtkiow8x64.sys

Is rtkiow8x64.sys safe?

Based on DriverShield static and dynamic analysis, rtkiow8x64.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.

What is the risk score of rtkiow8x64.sys?

rtkiow8x64.sys has a DriverShield composite risk score of 72/100, placing it in the vulnerable verdict band. SHA256: b205835b818d8a50903cf76936fcf8160060762725bd74a523320cfbd091c038.

What is rtkiow8x64.sys?

rtkiow8x64.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


DriverShield © 2025-2026 · Terms · Privacy · Contact