f16b44cca74d3c3645e4c0a6bb5c0c... - Vulnerable (72/100) - DriverShield Analysis

Analysis of f16b44cca74d3c3645e4c0a6bb5c0cb9.sys: vulnerable verdict, risk score 72/100. 3 YARA matches, 1/76 multi-engine detections. SHA256 7e81beae78e1ddbf. Kernel imports, IOCTL codes, MITRE ATT&CK, and code-signing details.

f16b44cca74d3c3645e4c0a6bb5c0cb9.sys - Analysis Report

DriverShield analyzed the Windows kernel driver f16b44cca74d3c3645e4c0a6bb5c0cb9.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 detections1 / 76
File size71152 bytes
Code-signing signerSymantec Time Stamping Services CA - G2
Analyzed2026-05-29
SHA2567e81beae78e1ddbf6c150e15667e1f18783f9b0ab7fbe52c7ab63e754135948d
SHA1eceb51233f013e04406da11482324d45e70281c7
MD5f16b44cca74d3c3645e4c0a6bb5c0cb9

Driver identity

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

File descriptionAMD Ryzen Master Service Driver
ProductAMD Ryzen Master Service Driver
CompanyAdvanced Micro Devices
Original filenameAMDRyzenMasterDriver.sys
Internal nameAMDRyzenMasterDriver.sys
File version1.3.0.0
CopyrightCopyright © 2018 AMD, Inc.

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 surface48 / 100
Known-vulnerable corpus100 / 100
Code-signing state80 / 100
Packing and entropy0 / 100
Dynamic behaviour0 / 100
CVE cross-reference0 / 100

Kernel imports (22)

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

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

IOCTL dispatch codes (16)

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
0x002200F0mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #60
0x0080FF0DmediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #4035
0x00225A84mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1697
0x002297E9mediumMETHOD_IN_DIRECTFILE_DEVICE_UNKNOWN Function #1530
0x00802484mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2337
0x00802494mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2341
0x0080DF15mediumMETHOD_IN_DIRECTFILE_DEVICE_CUSTOM Function #1989
0x00342444mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #2321
0x00220FE8mediumMETHOD_BUFFEREDFILE_DEVICE_UNKNOWN Function #1018
0x00802520mediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2376
0x00340030mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #12
0x00343D0EmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #3907
0x00343D2EmediumMETHOD_OUT_DIRECTFILE_DEVICE_DISK Function #3915
0x0080248CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2339
0x0080249CmediumMETHOD_BUFFEREDFILE_DEVICE_CUSTOM Function #2343
0x00340364mediumMETHOD_BUFFEREDFILE_DEVICE_DISK Function #217

PE sections

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

SectionVirtual sizeRaw sizeEntropyFlags
.text0x8BAA0x8C006.04CODE, EXEC, READ
.rdata0x0E100x10003.97IDATA, READ
.data0x20CB80x06002.29IDATA, READ, WRITE
.pdata0x051C0x06004.09IDATA, READ
.gfids0x00040x02000.02IDATA, READ
PAGE0x18FD0x1A006.27CODE, EXEC, READ
INIT0x06FE0x08004.69CODE, EXEC, READ, DISCARD
.rsrc0x03C80x04003.14IDATA, READ, DISCARD
.reloc0x00380x02000.69IDATA, READ, DISCARD

Exploit mitigations

Control Flow GuardNot enabled
ASLREnabled
DEPEnabled
Integrity checkNot enforced
Mitigation score55 / 100

YARA rule matches (3)

RuleSeverityDetects
PUA_VULN_Driver_Advancedmicrodevices_Amdryzenmasterdriversys_Amdryzenmasterservicedriver_A...mediumDetects vulnerable driver mentioned in known-vulnerable driver corpus project using VersionInfo values from the PE header - AMDRyzenMasterDriver.sys
BYOVD_MemRWcriticalPhys memory mapping + device creation
SUSP_PhysMemhighPhysical memory mapping

MITRE ATT&CK techniques (17)

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
T1014RootkitDefense Evasion
T1055.012Process HollowingDefense Evasion
T1068Exploitation for Privilege EscalationPrivilege Escalation
T1071Application Layer ProtocolCommand and Control
T1112Modify RegistryDefense Evasion
T1211Exploitation for Defense EvasionDefense Evasion
T1542.001Pre-OS Boot: System FirmwarePersistence
T1543.003Windows ServicePersistence
T1547.001Registry Run KeysPersistence
T1553.002Subvert Trust Controls: Code SigningDefense Evasion
T1562.001Impair DefensesDefense Evasion
T1569.002Service ExecutionExecution
T1601Modify System ImageDefense Evasion
T1652Device Driver DiscoveryDiscovery

Code-signing chain

SignerSymantec Time Stamping Services CA - G2
Signer organisationSymantec Corporation
IssuerThawte Timestamping CA
Serial7E93EBFB7CC64E59EA4B9A77D406FC3B
Valid from2012-12-21 00:00 UTC
Valid until2020-12-30 23:59 UTC (expired)
Signature validityNot verified

Symbolic execution

Engine angr, status static_approximation, 0 paths explored at a maximum depth of 0. Vulnerability classes reached: 0. 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.

Frequently asked questions about f16b44cca74d3c3645e4c0a6bb5c0cb9.sys

Is f16b44cca74d3c3645e4c0a6bb5c0cb9.sys safe?

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

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

What is f16b44cca74d3c3645e4c0a6bb5c0cb9.sys?

f16b44cca74d3c3645e4c0a6bb5c0cb9.sys is a Windows kernel-mode driver (.sys) analyzed by DriverShield for vulnerabilities, BYOVD abuse potential, and malware indicators. It is code-signed by Symantec Time Stamping Services CA - G2.

Related: Other drivers signed by Symantec Time Stamping Services CA - G2 · 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