# CVE-2022-4990: Privilege escalation in AI Suite 3

> Local attackers can escalate privileges by bypassing security validation in the ASUS AI Suite 3 driver via crafted IOCTL requests.

- **Severity:** High 7.3 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-8fqj-x6jv-392p

## What is CVE-2022-4990?

CVE-2022-4990 is a high-severity vulnerability in ASUS AI Suite 3, published on 3 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

** UNSUPPORTED WHEN ASSIGNED ** Improper Validation of Specified Quantity in Input in the ASUS AI Suite 3 driver allows a local user to bypass security validation and access restricted memory blocks via crafted IOCTL requests, leading to privilege escalation.
Refer to the 'End-of-Life Notice and Driver Update for Legacy ASUS Drivers ' section on the ASUS Security Advisory for more information.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2022-4990?


## How do I fix CVE-2022-4990?

No fix has been published for CVE-2022-4990 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4990 being exploited?

There is no known exploitation of CVE-2022-4990 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4990 and fix it if it is affected.

What it is: CVE-2022-4990 is a high-severity vulnerability in ASUS AI Suite 3, published on 3 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4990 in the wild and no public exploit code.

Affected product: ASUS AI Suite 3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4990/ (Markdown: https://insights.sbomify.com/CVE-2022-4990/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4990
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4990
- OSV: https://osv.dev/vulnerability/CVE-2022-4990

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4990/
Summaries are generated and may contain mistakes; the official description above is the record.