# CVE-2026-74730: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call

> A use-after-free vulnerability in the Linux kernel's NFS implementation allows attackers to potentially execute code or escalate privileges via delayed FREE_STATEID operations.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 22 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-97275, BELL-CVE-2026-74730, DEBIAN-CVE-2026-74730, GHSA-rmc7-77jw-fvm4, UBUNTU-CVE-2026-74730

## What is CVE-2026-74730?

CVE-2026-74730 is a critical use after free vulnerability in Linux, published on 22 Aug 2026. 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:

NFS: Pin the 'struct nfs_server' during a FREE_STATEID call

Dan Aloni reports that he was able to hit a use-after-free bug if a
FREE_STATEID operation gets delayed for whatever reason. Fix this by
bumping the refcount of the 'struct nfs_server' object for the duration
of the FREE_STATEID so it doesn't get cleaned up from underneath us
while operations are still in flight.

## Which versions are affected by CVE-2026-74730?


## How do I fix CVE-2026-74730?

Apply the vendor's patch.

## Is CVE-2026-74730 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74730 and fix it if it is affected.

What it is: CVE-2026-74730 is a critical use after free vulnerability in Linux, published on 22 Aug 2026. 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-2026-74730 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-2026-74730/ (Markdown: https://insights.sbomify.com/CVE-2026-74730/index.md)
```

## Sources

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

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