# CVE-2022-50861: NFSD: Finish converting the NFSv2 GETACL result encoder

> A flaw in the Linux kernel NFS server leaks stale memory contents to clients due to incorrect buffer length handling in the GETACL encoder.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50861, GHSA-fvjx-6c9m-3p89, UBUNTU-CVE-2022-50861

## What is CVE-2022-50861?

CVE-2022-50861 is a high-severity 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:

NFSD: Finish converting the NFSv2 GETACL result encoder

The xdr_stream conversion inadvertently left some code that set the
page_len of the send buffer. The XDR stream encoders should handle
this automatically now.

This oversight adds garbage past the end of the Reply message.
Clients typically ignore the garbage, but NFSD does not need to send
it, as it leaks stale memory contents onto the wire.

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


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

Apply the vendor's patch.

## Is CVE-2022-50861 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50861 is a high-severity 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-50861 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-50861/ (Markdown: https://insights.sbomify.com/CVE-2022-50861/index.md)
```

## Sources

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

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