CVE-2026-89688
nfsd: drop the stateid, not the stateowner, on seqid_op replay retry
Reported by linux · Published September 11, 2026
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.
EPSS 0.74% · 55.4th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel6.18-modules-extra-common | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | eec7620800081e27dbf8019ac2e66259f0d5bf6f, eec7620800081e27dbf8019ac2e66259f0d5bf6f, eec7620800081e27dbf8019ac2e66259f0d5bf6f |
| Linux | Linux | 6.10, 0, 6.12.109 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| linux | linux_kernel | 6.10, 6.10, 6.10 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | kernel-livepatch-6.18.51-120.162 | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | python3-perf6.12 | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| Linux | Linux | 7.3, *, * |
| amazon:2023 | perf6.12 | 0 |
…and 7 more
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (29 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-89688
vulnetix vdb fixes CVE-2026-89688
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-89688/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart