# OSV-2022-475: Heap-double-free in nft_set_context_free_many

> A heap double-free vulnerability in network library functions allows attackers to cause denial of service or potentially execute arbitrary code.

- **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:** 13 Jun 2022

## What is OSV-2022-475?

OSV-2022-475 is an use after free vulnerability in systemd, published on 13 Jun 2022. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47973

```
Crash type: Heap-double-free
Crash state:
nft_set_context_free_many
network_unref
network_load_one
```

## Which versions are affected by OSV-2022-475?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `systemd` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2022-475?

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

## Is OSV-2022-475 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2022-475 and fix it if it is affected.

What it is: OSV-2022-475 is an use after free vulnerability in systemd, published on 13 Jun 2022. 
Exploitation: There is no known exploitation of OSV-2022-475 in the wild and no public exploit code.

Affected packages and fixed versions:
- systemd (OSS-Fuzz): 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/OSV-2022-475/ (Markdown: https://insights.sbomify.com/OSV-2022-475/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2022-475

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