Gigabyte warns of GCC kernel vulnerability: update strongly recommended for Control Center

Published 3 min read
Schwarze Gigabyte-Grafikkarte in einem PC-System
Image: Rafael Pol / Unsplash · Image source

Gigabyte has confirmed a new security vulnerability in the GIGABYTE Control Center (GCC) that allows an attacker who is already logged in locally to gain extensive access to the Windows kernel and the underlying hardware. Affected are the kernel drivers GVCIDrv64.sys and gdrv3.sys, which are part of the Gigabyte software.

The manufacturer rates the issue with a CVSS score of 8.8 as ‘High’ and explicitly recommends that users bring GCC up to the current version. A corrected build is already available.

What exactly is vulnerable?

According to Gigabyte’s own security notice, the cause lies in the IOCTL interfaces of the two kernel drivers. Sufficient access controls and input validation were missing there. An authenticated local attacker can therefore send specially crafted requests to the driver and, among other things, map physical memory or access hardware interfaces directly.

This matters because kernel drivers under Windows operate with very high privileges. Anyone who can abuse their interfaces no longer operates at the normal privilege level of a desktop application. Gigabyte cites as possible consequences local privilege escalation, unauthorised hardware configuration and, in the worst case, complete compromise of the system.

Not an ‘attack from the internet’ without local access

The risk assessment nevertheless needs some context. According to Gigabyte’s CVSS vector, this is a local attack vector: the attacker must already be able to run code on the computer or be authenticated locally. It is therefore not a vulnerability with which arbitrary websites or remote systems can take over a fully unpatched PC without further access.

The flaw becomes problematic mainly as a building block in an attack chain. Malware that initially runs only with restricted user rights could, for example, use a vulnerable driver to penetrate deeper into the system and bypass operating system protection mechanisms.

These versions close the vulnerability

Gigabyte names two minimum versions for the updated components: GIGABYTE Control Center 26.08.28.01 or GBT_VGA 26.08.24.01 or newer. The company advises affected users either to update via GCC LiveUpdate or to install the current software from the support page of the relevant Gigabyte product.

On current German support pages, Gigabyte now provides complete packages containing GCC Main Program 26.08.28.01 and VGA 26.08.24.01 or newer components. Anyone who has GCC installed should therefore not only check the visible main version but update the entire package via LiveUpdate or the product support page.

Gigabyte hardens the driver interfaces

For the corrected versions, Gigabyte describes several changes: unnecessary high-risk interfaces for direct physical memory mapping have been removed, hardware access requires additional privilege checks, and IOCTL inputs are validated more strictly. This is intended to block requests for sensitive hardware registers and configuration areas.

The security vulnerability is also not identical to CVE-2026-9492, which Gigabyte had only published at the beginning of September for the separate MyPortIO_x64.sys driver in the DRAM Lighting module of the Control Center. There too, local attackers could access physical memory via inadequately secured IOCTL commands. For this older issue, Gigabyte names MBStorage_26.09.08.01 or newer as the corrected version.

What users should do now

Anyone who has GIGABYTE Control Center installed on a gaming PC or laptop should open the application and search for updates via LiveUpdate. Alternatively, the current GCC package can be downloaded from the support page of the relevant motherboard, graphics card or laptop.

According to Gigabyte’s current status, no manual workaround is needed once the updated drivers are installed. Users who do not use GCC do not need to install it additionally for the fix. What matters is that on systems with GCC no old, vulnerable driver versions remain.

Source: Gigabyte Security Advisory, 21 September 2026.

Write a comment
Your name and comment are public. The email address is optional and will not be published.