# GSD-2022-1005682: ksmbd: fix memory leak in smb2_handle_negotiate

> A memory leak in the ksmbd SMB server allows remote attackers to cause a denial of service by exhausting kernel memory.

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

## What is GSD-2022-1005682?

GSD-2022-1005682 is a denial of service vulnerability in Kernel, published on 17 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ksmbd: fix memory leak in smb2_handle_negotiate

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.15.61 by commit dd4e4c811898410e6a3ae3b63207b7c542860907, it was introduced in version v5.15 by commit e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9. For more details please see the references link.

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

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

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

## Is GSD-2022-1005682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: GSD-2022-1005682 is a denial of service vulnerability in Kernel, published on 17 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GSD-2022-1005682 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-1005682/ (Markdown: https://insights.sbomify.com/GSD-2022-1005682/index.md)
```

## Sources

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

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