GIGABYTE Multiple Products Unspecified Vulnerability (CVE-2018-19320)

What is affected, what to do

The GDrv low-level driver in GIGABYTE 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 exposes ring0 memcpy-like functionality that could allow a local attacker to take complete control of the affected system.

The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update Gigabyte Aorus Graphics Engine to version 1.57, Gigabyte App Center to version 19.0422.1, Gigabyte Xtreme Gaming Engine to version 1.26. Immediate actions, mitigation and detection rules are in the runbook below.

Affected

• Gigabyte Aorus Graphics Engine lt *..1.57
• Gigabyte App Center lt *..19.0422.1
• Gigabyte OC Guru II eq 2.08..2.08
• Gigabyte Xtreme Gaming Engine lt *..1.26

Fixed in

• Gigabyte Aorus Graphics Engine 1.57
• Gigabyte App Center 19.0422.1
• Gigabyte Xtreme Gaming Engine 1.26

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

Response and mitigation

1. 01

   Runbook step 1

   Immediate response (0-24 h)

   • Hunt fleet-wide: Use EDR or software inventory to find gdrv.sys (service usually named gdrv) and installations of GIGABYTE App Center, AORUS Graphics Engine, XTREME Gaming Engine and OC GURU II. Expect hits on gaming-grade hardware, engineering workstations and BYOD-adjacent devices. Do not rely on file path — attackers commonly drop the driver into %TEMP% or C:\Windows\.
   • Upgrade or uninstall: Move AORUS Graphics Engine to 1.57 or later and XTREME Gaming Engine to 1.26 or later. App Center v1.05.21 and earlier is affected; verify the current release. The context gives no fixed version for OC GURU II, so uninstall it — it rarely has a business purpose on corporate endpoints. For all products: patch available from the vendor — check the vendor advisory for the exact version.
   • Remove the driver: Stop and delete the service (sc stop gdrv && sc delete gdrv), remove the .sys file and reboot. Uninstalling the application does not always unload or delete the kernel driver.
   • Treat unexpected hits as an incident: Any gdrv.sys on a host without GIGABYTE software indicates BYOVD (Bring Your Own Vulnerable Driver).
     • Network-isolate the host immediately and capture memory and disk.
     • Check whether EDR, AV or backup agents were killed.
     • Rotate local and domain credentials used on that host.
   • Prepare for ransomware: Verify that offline and immutable backups are intact — kernel access is typically used to blind security tooling before encryption.
2. 02

   Runbook step 2

   Mitigation layers

   • Driver blocklisting: Enable the Microsoft Vulnerable Driver Blocklist (Windows Security → Device security → Core isolation). Add your own WDAC/App Control deny rule for gdrv.sys by hash and signer, sourcing hashes from LOLDrivers.io or your own finding.
   • Endpoint hardening:
     • Enforce HVCI (Memory Integrity) and Secure Boot.
     • Deploy the Defender ASR rule "Block abuse of exploited vulnerable signed drivers" (56a863a9-875e-4185-98a7-b882c64b5ce5) in block mode.
     • Turn on EDR tamper protection.
   • IAM/least privilege: Loading a driver requires admin rights (SeLoadDriverPrivilege). Strip local admin, deploy LAPS and gate admin sessions through PAM and tiering. This breaks the chain "low-priv foothold → privilege escalation → driver load".
   • Software control: Ban GIGABYTE and other hardware-tuning utilities on managed clients via AppLocker/WDAC or your software-distribution policy.
   • Segmentation: Place hosts that genuinely depend on these tools, such as specialised workstations, in a dedicated VLAN. On that VLAN, block inbound RDP/SMB from client networks and restrict egress to defined services, to contain lateral movement after kernel compromise.
3. 03

   Runbook step 3

   Detection rules

   • Sysmon EID 6 (driver loaded): Alert when ImageLoaded ends with gdrv.sys or Signature contains "GIGA-BYTE" on non-approved hosts. Sigma shape: logsource: product: windows, category: driver_load | detection: ImageLoaded|endswith: '\gdrv.sys'.
   • Service installation: System EID 7045 or Security EID 4697 with a kernel-mode driver service type and an ImagePath outside C:\Windows\System32\drivers\. KQL: DeviceEvents | where ActionType == "DriverLoad" | where FileName =~ "gdrv.sys".
   • Process ancestry: sc.exe create … type= kernel or NtLoadDriver calls originating from script hosts (powershell.exe, cmd.exe, rundll32.exe) or from unsigned binaries in %TEMP%, %APPDATA% or C:\ProgramData\.
   • Follow-on behaviour: Security services stopping or crashing (System EIDs 7034/7036) shortly after a driver load. Also flag shadow-copy deletion that follows (vssadmin delete shadows, wmic shadowcopy delete).
   • File system: Sysmon EID 11 for *.sys files written by non-installer processes. SPL: index=sysmon EventCode=11 TargetFilename="*.sys" NOT Image IN ("*\\msiexec.exe","*\\TrustedInstaller.exe").

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2

NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

Read in glossary

Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).

CRA

The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

Read in glossary

Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.

ISO/IEC 27001

ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

Read in glossary

Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

The GDrv low-level driver in GIGABYTE 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 exposes ring0 memcpy-like functionality that could allow a local attacker to take complete control of the affected system.

Source: CISA KEV Catalog, cvelistv5, NVD (NIST)

Vendors and products

• Gigabyte Gigabyte Aorus Graphics Engine
• Gigabyte Gigabyte App Center
• Gigabyte Gigabyte OC Guru II
• Gigabyte Gigabyte Xtreme Gaming Engine

References & sources

• seclists.org20181221 [CORE-2018-0007] - GIGABYTE Driver Elevation of Privilege VulnerabilitiesMailing list, x_refsource_FULLDISC
• secureauth.comlabs/advisories/gigabyte-drivers-elevation-privilege-vulnerabil…x_refsource_MISC
• securityfocus.com106252Vulnerability database, x_refsource_BID
• gigabyte.comtw/Support/Utility/Graphics-Cardx_refsource_CONFIRM
• gigabyte.comSupport/Security/1801x_refsource_CONFIRM
• cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2018-19320government-resource