# CVE-2017-5957: Memory corruption in n/a

> A local guest user can crash the application via a stack-based buffer overflow in virglrenderer used by QEMU.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 14 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5957, GHSA-97qh-pwfw-7gj4

## What is CVE-2017-5957?

CVE-2017-5957 is a medium-severity memory corruption vulnerability in n/a, published on 14 Mar 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in the vrend_decode_set_framebuffer_state function in vrend_decode.c in virglrenderer before 926b9b3460a48f6454d8bbe9e44313d86a65447f, as used in Quick Emulator (QEMU), allows a local guest users to cause a denial of service (application crash) via the "nr_cbufs" argument.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2017-5957?

It affects 1 product.


Products: Virglrenderer Project Virglrenderer.

## How do I fix CVE-2017-5957?

Apply the vendor's patch.

## Is CVE-2017-5957 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5580](https://insights.sbomify.com/CVE-2017-5580/): Memory corruption in n/a (high 7.1)
- [CVE-2016-10214](https://insights.sbomify.com/CVE-2016-10214/): Denial of service in n/a (medium 6.5)
- [CVE-2016-10163](https://insights.sbomify.com/CVE-2016-10163/): Denial of service in n/a (medium 6.5)
- [CVE-2017-5937](https://insights.sbomify.com/CVE-2017-5937/): Null dereference in n/a (medium 6.5)
- [CVE-2017-5993](https://insights.sbomify.com/CVE-2017-5993/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5957 and fix it if it is affected.

What it is: CVE-2017-5957 is a medium-severity memory corruption vulnerability in n/a, published on 14 Mar 2017. 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-2017-5957 in the wild and no public exploit code.

Affected product: n/a. 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-2017-5957/ (Markdown: https://insights.sbomify.com/CVE-2017-5957/index.md)
```

## Sources

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

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