Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2018-19320: Arbitrary kernel memory access in GIGABYTE GDrv

Published Dec 21, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS4.6%92nd percentile
CISA KEVYesAdded Oct 24, 2022
In the wildActivePer CISA KEV
Vendor
GIGABYTE Technology
IdentifiersCVE-2018-19320CWE-123

CVE-2018-19320 is an arbitrary kernel memory access vulnerability in the GIGABYTE GDrv low-level Windows driver distributed with APP Center v1.05.21 and earlier, AORUS GRAPHICS ENGINE before 1.57, XTREME GAMING ENGINE before 1.26, and OC GURU II v2.08. The driver exposes ring-0 memcpy-like functionality that permits arbitrary memory reads and writes, allowing a local attacker to escalate privileges and take complete control of the affected system. RobbinHood ransomware has exploited the vulnerability to modify kernel memory, temporarily disable Windows driver signature enforcement, and load an unsigned malicious kernel driver.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises kernel memory confidentiality and integrity and can give an attacker complete control of the affected Windows system. Observed exploitation disabled driver signature enforcement and enabled an unsigned malicious driver to terminate endpoint-security processes and delete their supporting files from kernel mode, bypassing tamper protection and facilitating ransomware encryption.

Mitigation

If you can’t patch tonight, do this now.

Block the vulnerable driver through enforced driver-control policies and maintain vulnerable-driver blocklists. Monitor installed and newly loaded drivers, keep supported drivers updated, and investigate driver loading followed by security-process termination. HVCI and driver blocklisting provide layered defenses against vulnerable-driver abuse; a valid digital signature alone does not establish driver safety.

Remediation

Patch, then assume compromise.

Remove the discontinued vulnerable GIGABYTE driver and uninstall or replace affected software that installs it. A verified fixed driver release is not established by the available information.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2018-19320-LPEThis repository contains a local privilege escalation (LPE) exploit for CVE-2018-19320, targeting vulnerable GIGABYTE drivers (gdrv.sys) on Windows systems. The main exploit code is implemented in C++ (CVE-2018-19320-LPE-Exploit.cpp) and is designed to be built with Visual Studio. The exploit works by opening a handle to the vulnerable driver (\\.\GIO), allocating kernel memory, and writing custom shellcode that steals the SYSTEM process token. It then overwrites a function pointer in the HalDispatchTable to point to the shellcode, triggers execution via NtQueryIntervalProfile, and restores the original pointer to avoid system instability. Upon success, it launches a SYSTEM-level command prompt. The exploit specifically targets GIGABYTE software products with vulnerable driver versions, as listed in the README. The repository includes project files for building the exploit and a README with usage context and affected versions. No network endpoints are involved; the attack vector is purely local, requiring execution on a vulnerable system.hmnthabit · Disclosed Aug 19, 2021 · c++ · localOperationalGDRVLoaderThis repository is a Windows kernel exploit tool designed to load or unload unsigned drivers on Windows 10 and 11 systems. The main entry point is 'GDRVLoader.cpp', which provides a command-line interface for users to specify a target driver to load or unload. The tool works by dropping a vulnerable Gigabyte driver (gdrv.sys) to 'C:\Windows\System32\Drivers\gdrv.sys', loading it, and then exploiting its IOCTL interface (\Device\GIO) to manipulate kernel memory and disable Driver Signature Enforcement (DSE). This allows arbitrary unsigned drivers to be loaded, bypassing Windows security mechanisms such as PatchGuard and DSE. The exploit logic and kernel manipulation are primarily implemented in 'exploit/swind2.cpp', while 'exploit/pe.cpp' provides PE file mapping and export resolution utilities. The repository also includes a custom implementation of the Hacker Disassembler Engine (hde64) for binary analysis. The tool requires administrator privileges and is intended for advanced users or researchers needing to load unsigned drivers for testing or exploitation purposes. No network endpoints are present; all actions are performed locally on the target system.zer0condition · Disclosed Nov 12, 2022 · c++ · c · localOperationalmegumin.exeThis standalone Windows BYOVD repository contains 16 files: five C source files, five headers, a Makefile, three Visual Studio solution/project files, README.md, and .gitignore. Its entry point is main.c. gio.c manages the vulnerable Gigabyte driver and exposes arbitrary kernel-memory copying; eprocess.c resolves build-specific protection offsets and obtains the target EPROCESS address from a process handle using NtQuerySystemInformation class 64. main.c reads and zeroes the protection byte, then optionally invokes credential or dump routines. This is an administrator-level local protection bypass, not an unauthenticated remote exploit; network functionality is optional outbound dump exfiltration. The follow-on capabilities are substantive: dump_direct.c implements build-dependent LSASS pattern scanning and MSV1_0 credential extraction using dynamically resolved BCrypt functions. dump_remote.c implements shared local-file/TCP output and a custom minidump builder, with visible code enumerating readable committed memory and process modules and resolving NtReadVirtualMemory dynamically. It avoids MiniDumpWriteDump and dbghelp; resolving the ntdll export does not itself establish a direct-syscall or comprehensive hook bypass. Headers define minidump structures, credential layouts, native API types, and driver IOCTL structures. Cleanup attempts to unload/delete the GIO service, but leaves process protection disabled and does not delete the driver file. Important limitations: the driver binary is absent; portions of dump_direct.c and dump_remote.c are truncated in the supplied content, so their complete implementations cannot be verified. The README reports testing only on Windows Server 2019 build 17763. Although direct-mode tables include Windows 11 build 26100, the mandatory protection-offset table lacks that build, so the normal entry point exits before exploitation there. Server 2022 has a protection offset but no matching visible direct-mode key table. The implementation uses x64-specific layouts despite Win32 project configurations. The Makefile references src/ and include/ directories absent from the supplied layout and therefore needs adjustment. Repository URL, git reference, and archive size were not supplied; empty metadata and a zero size are placeholders.saretawa · Disclosed Nov 11, 2026 · c · local · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GIGABYTE TechnologyAorus Graphics Engineapplication
GIGABYTE TechnologyApp Centerapplication
GIGABYTE TechnologyOc Guru Iiapplication
GIGABYTE TechnologyXtreme Gaming Engineapplication
FAQ

Frequently asked questions

Is CVE-2018-19320 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Oct 24, 2022.
Is there a public exploit for CVE-2018-19320?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2018-19320, the earliest disclosed Aug 19, 2021.
Is there a patch for CVE-2018-19320?
Remove the discontinued vulnerable GIGABYTE driver and uninstall or replace affected software that installs it. A verified fixed driver release is not established by the available information.
What products are affected by CVE-2018-19320?
GIGABYTE Technology Aorus Graphics Engine, GIGABYTE Technology App Center, GIGABYTE Technology Oc Guru Ii, and GIGABYTE Technology Xtreme Gaming Engine.
How severe is CVE-2018-19320?
CVE-2018-19320 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 4.6% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
codebyNews · Oct 7, 2026SilverFox BYOVD: обход антивируса невидимым драйверомA vulnerability in Gigabyte's gdrv.sys driver used in BYOVD attacks. The article reports CVSS 7.8 and active exploitation, including ransomware use, but does not explain the underlying flaw.Read more ↗sophos threat researchNews · Jan 1, 2026Living off another land: Ransomware borrows vulnerable driver to remove security software | SOPHOSA privilege escalation / arbitrary kernel memory read-write vulnerability in Gigabyte's signed GDRV.SYS driver that attackers abused to disable Windows driver signature enforcement and load an unsigned malicious driver during RobbinHood ransomware attacks.Read more ↗the hacker newsNews · Oct 7, 2022BlackByte Ransomware Abuses Vulnerable Windows Driver to Disable Security SolutionsA vulnerability in the gdrv.sys driver cited as a historical example of ransomware abusing vulnerable drivers to terminate endpoint protection processes. The article collectively references RobbinHood and AvosLocker alongside gdrv.sys and asWarPot.sys without explicitly mapping each ransomware family to an individual driver vulnerability.Read more ↗threatpostNews · Feb 10, 2020BYO-Bug Tactic Attacks Windows Kernel with Outdated Driver | ThreatpostA privilege-escalation vulnerability in Gigabyte's GDRV.SYS driver permits arbitrary memory reads and writes. RobbinHood abuses it to modify kernel memory, disable driver signature enforcement, and load a malicious driver that terminates endpoint-security processes and deletes their files before ransomware encryption. Although Gigabyte discontinued the vulnerable driver in 2018, its signing certificate remained valid.Read more ↗
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.