# GSD-2021-1000513: uio_hv_generic: Fix a memory leak in error handling paths

> A memory leak in the uio_hv_generic driver error handling paths can lead to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 31 May 2021

## What is GSD-2021-1000513?

GSD-2021-1000513 is a memory corruption vulnerability in Kernel, published on 31 May 2021. 

### Official description

uio_hv_generic: Fix a memory leak in error handling paths

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.4.122 by commit cdd91637d4ef33e2be19a8e16e72e7d00c996d76, it was introduced in version v4.20 by commit cdfa835c6e5e87d145f9f632b58843de97509f2b. For more details please see the references link.

## Which versions are affected by GSD-2021-1000513?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2021-1000513?

No fix has been published for GSD-2021-1000513 yet. Limit exposure of the affected software until one is available.

## Is GSD-2021-1000513 being exploited?

There is no known exploitation of GSD-2021-1000513 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2021-1000513 and fix it if it is affected.

What it is: GSD-2021-1000513 is a memory corruption vulnerability in Kernel, published on 31 May 2021. 
Exploitation: There is no known exploitation of GSD-2021-1000513 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2021-1000513/ (Markdown: https://insights.sbomify.com/GSD-2021-1000513/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2021-1000513

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