# CVE-2022-0175: Information disclosure in virglrenderer

> A malicious guest can read uninitialized host memory via the VirGL renderer, leading to information disclosure.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** Yes
- **Published:** 26 Aug 2022
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-10772, AZL-35347, GHSA-28q3-mx7c-4cc3, OESA-2022-1776, SUSE-SU-2022:0110-1, SUSE-SU-2022:0111-1, UBUNTU-CVE-2022-0175, openSUSE-SU-2022:0111-1, openSUSE-SU-2024:11770-1

## What is CVE-2022-0175?

CVE-2022-0175 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 26 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the VirGL virtual OpenGL renderer (virglrenderer). The virgl did not properly initialize memory when allocating a host-backed memory resource. A malicious guest could use this flaw to mmap from the guest kernel and read this uninitialized memory from the host, possibly leading to information disclosure.

Weakness: CWE-909 (Missing Initialization of Resource)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virglrenderer` | SUSE:Linux Enterprise Micro 5.0 | All versions | 0.6.0-4.6.1 |
| `virglrenderer` | SUSE:Linux Enterprise Module for Server Applications 15 SP3 | All versions | 0.6.0-4.6.1 |
| `virglrenderer` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 0.5.0-12.6.1 |
| `virglrenderer` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 0.5.0-12.6.1 |
| `virglrenderer` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 0.5.0-12.6.1 |
| `virglrenderer` | openSUSE:Leap 15.3 | All versions | 0.6.0-4.6.1 |

Products: Redhat Enterprise Linux, Virglrenderer Project Virglrenderer.

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

Apply the vendor's patch.

## Is CVE-2022-0175 being exploited?

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

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2018-14667](https://insights.sbomify.com/CVE-2018-14667/): Red Hat JBoss RichFaces Framework Expression Language Injection (critical 9.8, exploited in the wild)
- [CVE-2021-20325](https://insights.sbomify.com/CVE-2021-20325/): Missing fixes for CVE-2021-40438 and CVE-2021-26691 in the versions of httpd, as shipped in Red Hat Enterprise Linux 8.5.0, causes a securit (critical 9.8)
- [CVE-2018-25011](https://insights.sbomify.com/CVE-2018-25011/): Memory corruption in libwebp (critical 9.8)
- [CVE-2018-25014](https://insights.sbomify.com/CVE-2018-25014/): Other in libwebp (critical 9.8)
- [CVE-2014-3585](https://insights.sbomify.com/CVE-2014-3585/): Supply chain in redhat-upgrade-tool (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0175 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 26 Aug 2022. 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-0175 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-0175/ (Markdown: https://insights.sbomify.com/CVE-2022-0175/index.md)
```

## Sources

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

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