# GSD-2023-1001708: nfsd: fix handling of cached open files in nfsd4_open codepath

> A bug in the Linux Kernel NFS server's handling of cached open files can lead to potential denial of service issues.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2023

## What is GSD-2023-1001708?

GSD-2023-1001708 is a vulnerability in Kernel, published on 31 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

nfsd: fix handling of cached open files in nfsd4_open codepath

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 v6.1.7 by commit 973acfdfe90c8a4e58ade97ff0653a498531ff2e, it was introduced in version v5.19 by commit fb70bf124b051d4ded4ce57511dfec6d3ebf2b43. For more details please see the references link.

## Which versions are affected by GSD-2023-1001708?

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-2023-1001708?

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

## Is GSD-2023-1001708 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2023-1001708 and fix it if it is affected.

What it is: GSD-2023-1001708 is a vulnerability in Kernel, published on 31 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2023-1001708 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-2023-1001708/ (Markdown: https://insights.sbomify.com/GSD-2023-1001708/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2023-1001708

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