# CVE-2022-48829: NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes

> An integer overflow in Linux kernel NFSv3 handling allows attackers to corrupt file size values, leading to unexpected data modification.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2024
- **Updated:** 14 Oct 2026
- **Also known as:** DEBIAN-CVE-2022-48829, GHSA-2294-53w4-gch9, UBUNTU-CVE-2022-48829

## What is CVE-2022-48829?

CVE-2022-48829 is a critical vulnerability in Linux kernel, published on 16 Jul 2024. 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: Fix NFSv3 SETATTR/CREATE's handling of large file sizes

iattr::ia_size is a loff_t, so these NFSv3 procedures must be
careful to deal with incoming client size values that are larger
than s64_max without corrupting the value.

Silently capping the value results in storing a different value
than the client passed in which is unexpected behavior, so remove
the min_t() check in decode_sattr3().

Note that RFC 1813 permits only the WRITE procedure to return
NFS3ERR_FBIG. We believe that NFSv3 reference implementations
also return NFS3ERR_FBIG when ia_size is too large.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2022-48829 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-48829 is a critical vulnerability in Linux kernel, published on 16 Jul 2024. 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-48829 in the wild and no public exploit code.

Affected product: Linux kernel. 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-48829/ (Markdown: https://insights.sbomify.com/CVE-2022-48829/index.md)
```

## Sources

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

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