# GSD-2021-1000876: tracing: Correct the length check which causes memory corruption

> A length check error in the Linux kernel tracing subsystem can lead to memory corruption, potentially allowing code execution or system crashes.

- **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:** 30 Jun 2021

## What is GSD-2021-1000876?

GSD-2021-1000876 is a memory corruption vulnerability in Kernel, published on 30 Jun 2021. 

### Official description

tracing: Correct the length check which causes memory corruption

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 v4.19.195 by commit 31ceae385556c37e4d286cb6378696448f566883, it was introduced in version v4.19.177 by commit 0572fc6a510add9029b113239eaabf4b5bce8ec9. For more details please see the references link.

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

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-1000876?

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

## Is GSD-2021-1000876 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2021-1000876 is a memory corruption vulnerability in Kernel, published on 30 Jun 2021. 
Exploitation: There is no known exploitation of GSD-2021-1000876 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-1000876/ (Markdown: https://insights.sbomify.com/GSD-2021-1000876/index.md)
```

## Sources

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

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