CyberSecBulletin
CVE-2026-9492NVD status: Deferred

MBStorage: Exposed IOCTL with Insufficient Access Control

CVE-2026-9492 is a high-severity exposed IOCTL with insufficient access control vulnerability in MBStorage from Gigabyte, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected MBStorage versions: 26.02.10.01 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.16% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of MBStorage you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
GIGABYTEMBStorage26.02.10.01 and earlierNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.org.tw).

Scoring systemScoreSeverityScored by
CVSS 4.08.5HighCNA (cert.org.tw)
CVSS 3.17.8HighCNA (cert.org.tw)

Official description

The MBStorage DRAM lighting control module within Gigabyte Control Center (GCC) developed by GIGABYTE Technology has an Improper Access Control vulnerability. Authenticated local attackers can send specific IOCTL commands through the driver MyPortIO_x64.sys bundled with the module, thereby arbitrarily reading and writing physical memory and obtaining kernel-level privileges.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Exposed IOCTL with Insufficient Access Control

The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.

How developers prevent this class of flaw

  • In Windows environments, use proper access control for the associated device or device namespace. See References.

More Exposed IOCTL with Insufficient Access Control vulnerabilities (CWE-782)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Exposed IOCTL with Insufficient Access Control vulnerabilities

Spotted an error? Tell us.