# GSD-2022-1004711: tracing/histograms: Fix memory leak problem

> A memory leak in Linux kernel tracing histograms can lead to resource exhaustion and denial of service, requiring local privileged access to trigger.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2022

## What is GSD-2022-1004711?

GSD-2022-1004711 is a denial of service vulnerability in Kernel, published on 31 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

tracing/histograms: Fix memory leak problem

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.207 by commit ecc6dec12c33aa92c086cd702af9f544ddaf3c75, it was introduced in version v5.4.69 by commit e92c490f104993cea35e5f5d5108ac12df1850ac. For more details please see the references link.

## Which versions are affected by GSD-2022-1004711?

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-2022-1004711?

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

## Is GSD-2022-1004711 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-1004711 and fix it if it is affected.

What it is: GSD-2022-1004711 is a denial of service vulnerability in Kernel, published on 31 Jul 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 GSD-2022-1004711 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-2022-1004711/ (Markdown: https://insights.sbomify.com/GSD-2022-1004711/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-1004711

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