# GSD-2022-1008317: btrfs: fix inode list leak during backref walking at resolve_indirect_refs()

> A memory leak in the btrfs filesystem during backref walking 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:** 8 Dec 2022

## What is GSD-2022-1008317?

GSD-2022-1008317 is a memory corruption vulnerability in Kernel, published on 8 Dec 2022. 

### Official description

btrfs: fix inode list leak during backref walking at resolve_indirect_refs()

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.14.299 by commit b1dc9019bb5f89abae85645de1a2dd4830c1f8e9, it was introduced in version v3.5 by commit 3301958b7c1dae8f0f5ded63aa881e0b71e78464. For more details please see the references link.

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

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

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

## Is GSD-2022-1008317 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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