# CVE-2026-74316: NFSD: Handle layout stid in nfsd4_drop_revoked_stid()

> A missing case in the Linux kernel NFS server causes a memory leak when handling revoked layout state IDs, potentially leading to resource exhaustion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74316, DEBIAN-CVE-2026-74316, GHSA-2mq4-hj52-9fc6, UBUNTU-CVE-2026-74316

## What is CVE-2026-74316?

CVE-2026-74316 is a high-severity memory corruption vulnerability in Linux, published on 15 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:

NFSD: Handle layout stid in nfsd4_drop_revoked_stid()

nfsd4_drop_revoked_stid() has no SC_TYPE_LAYOUT case, so when a
client sends FREE_STATEID for an admin-revoked layout stid, the
default branch releases cl_lock and returns without unhashing or
releasing the stid.  The stid remains in the IDR and on the
per-client list until the client is destroyed.

Remove the layout stid from the per-client list and call
nfs4_put_stid() to drop the creation reference.  When the
refcount reaches zero, nfsd4_free_layout_stateid() handles the
remaining cleanup: cancelling the fence worker, removing from
the per-file list, and freeing the slab object.

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


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

Apply the vendor's patch.

## Is CVE-2026-74316 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74316 is a high-severity memory corruption vulnerability in Linux, published on 15 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-74316 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-74316/ (Markdown: https://insights.sbomify.com/CVE-2026-74316/index.md)
```

## Sources

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

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