# GSD-2022-1002613: NFSD: Fix potential use-after-free in nfsd_file_put()

> A use-after-free vulnerability in the Linux Kernel NFS server allows attackers to potentially execute code or cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2022

## What is GSD-2022-1002613?

GSD-2022-1002613 is an use after free vulnerability in Kernel, published on 28 Jun 2022. It can be exploited over the network, with no action from the victim.

### Official description

NFSD: Fix potential use-after-free in nfsd_file_put()

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.18.4 by commit 333dcc94ebf53f79f3dc0e7a7c16700bc7ff7e57, it was introduced in version v5.18 by commit 999397926ab3f78c7d1235cc4ca6e3c89d2769bf. For more details please see the references link.

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

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

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

## Is GSD-2022-1002613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2022-1002613 is an use after free vulnerability in Kernel, published on 28 Jun 2022. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2022-1002613 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-1002613/ (Markdown: https://insights.sbomify.com/GSD-2022-1002613/index.md)
```

## Sources

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

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