# CVE-2023-0198: Memory corruption in vGPU software (guest driver - Linux), vGPU software (Virtual GPU Manager - Citrix Hypervisor, VMware vSphere, Red Hat Enterprise Linux KVM), , NVIDIA Cloud Gaming (guest driver - Linux), NVIDIA Cloud Gaming (Virtual GPU Manager - Red Hat Enterprise Linux KVM)

> NVIDIA GPU driver vulnerability allows attackers to cause denial of service, disclose information, or tamper with data via memory buffer issues.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **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:** Yes
- **Published:** 1 Apr 2023
- **Updated:** 13 Feb 2025
- **Also known as:** DEBIAN-CVE-2023-0198, GHSA-pf5q-m667-fh8x, UBUNTU-CVE-2023-0198

## What is CVE-2023-0198?

CVE-2023-0198 is a medium-severity memory corruption vulnerability in Nvidia Virtual Gpu, published on 1 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer, where improper restriction of operations within the bounds of a memory buffer can lead to denial of service, information disclosure, and data tampering.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2023-0198?

It affects 1 product.


Products: Nvidia Virtual Gpu.

## How do I fix CVE-2023-0198?

Apply the vendor's patch.

## Is CVE-2023-0198 being exploited?

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

## Other vulnerabilities in Nvidia Virtual Gpu

- [CVE-2023-0189](https://insights.sbomify.com/CVE-2023-0189/): Privilege escalation in vGPU software (guest driver - Linux), NVIDIA Cloud Gaming (guest driver - Linux) (high 8.8)
- [CVE-2023-31027](https://insights.sbomify.com/CVE-2023-31027/): CVE (high 8.2)
- [CVE-2023-31017](https://insights.sbomify.com/CVE-2023-31017/): CVE (high 7.8)
- [CVE-2023-31019](https://insights.sbomify.com/CVE-2023-31019/): CVE (high 7.8)
- [CVE-2023-0182](https://insights.sbomify.com/CVE-2023-0182/): Memory corruption in vGPU software (guest driver - Windows), NVIDIA Cloud Gaming (guest driver - Windows) (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0198 and fix it if it is affected.

What it is: CVE-2023-0198 is a medium-severity memory corruption vulnerability in Nvidia Virtual Gpu, published on 1 Apr 2023. 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-2023-0198 in the wild and no public exploit code.

Affected product: Nvidia Virtual Gpu. 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-2023-0198/ (Markdown: https://insights.sbomify.com/CVE-2023-0198/index.md)
```

## Sources

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

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