# CVE-2022-50859: cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message

> An attacker can read uninitialized memory from the network via a malformed CIFS negotiate message, potentially leaking sensitive kernel data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50859, GHSA-4fwr-9cpg-j96h, UBUNTU-CVE-2022-50859

## What is CVE-2022-50859?

CVE-2022-50859 is a vulnerability in Linux, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message

Commit d5c7076b772a ("smb3: add smb3.1.1 to default dialect list")
extend the dialects from 3 to 4, but forget to decrease the extended
length when specific the dialect, then the message length is larger
than expected.

This maybe leak some info through network because not initialize the
message body.

After apply this patch, the VALIDATE_NEGOTIATE_INFO message length is
reduced from 28 bytes to 26 bytes.

## Which versions are affected by CVE-2022-50859?


## How do I fix CVE-2022-50859?

Apply the vendor's patch.

## Is CVE-2022-50859 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50859 and fix it if it is affected.

What it is: CVE-2022-50859 is a vulnerability in Linux, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50859 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2022-50859/ (Markdown: https://insights.sbomify.com/CVE-2022-50859/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50859
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50859
- OSV: https://osv.dev/vulnerability/CVE-2022-50859

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