CVE-2020-9756: Patriot Viper RGB Driver 1.1 and prior exposes IOCTL and allows insufficient access control

Q: How do I fix CVE-2020-9756?

viper rgb firmware: upgrade to newer than 1.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-9756 being exploited?

CVE-2020-9756 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-9756 affect?

CVE-2020-9756 affects viper rgb firmware. Severity is high (CVSS 7.8). Patriot Viper RGB Driver 1.1 and prior exposes IOCTL and allows insufficient access control. The IOCTL Codes 0x80102050 and 0x80102054 allows a local user with low privileges to read/write 1/2/4 bytes from or to an IO port. This could be le

Q: How urgent is CVE-2020-9756?

Priority 43/100. High severity; Public exploit reference

This month

HIGH 7.8UPGRADE

CVE-2020-9756 is a high-severity flaw (CVSS 7.8) affecting viper rgb firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Patriot Viper RGB Driver 1.1 and prior exposes IOCTL and allows insufficient access control. The IOCTL Codes 0x80102050 and 0x80102054 allows a local user with low privileges to read/write 1/2/4 bytes from or to an IO port. This could be leveraged in a number of ways to ultimately run code with elevated privileges.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Published	2020-03-06
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: patriotmemory

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-03-06 15:15 UTCPublished CVE record published
2026-06-17 03:28 UTCUpdated Record last modified

patriotmemory viper rgb firmware UPGRADE

Affected: <= 1.1

Fixed in: newer than 1.1

Safe to downgrade to: no unaffected older release

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-9756?

viper rgb firmware: upgrade to newer than 1.1. Exact commands for each OS are on this page.

Is CVE-2020-9756 being exploited?

CVE-2020-9756 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-9756 affect?

CVE-2020-9756 affects viper rgb firmware. Severity is high (CVSS 7.8). Patriot Viper RGB Driver 1.1 and prior exposes IOCTL and allows insufficient access control. The IOCTL Codes 0x80102050 and 0x80102054 allows a local user with low privileges to read/write 1/2/4 bytes from or to an IO port. This could be le

How urgent is CVE-2020-9756?

Priority 43/100. High severity; Public exploit reference

Related CVEs

CVE-2019-18845 HIGH 7.1 MITIGATE The MsIo64.sys and MsIo32.sys drivers in Patriot Viper RGB before 1.1 allow local users (including low integri

References

← Back to latest CVEs