CVE-2026-89676
In the Linux kernel, the following vulnerability has been resolved: …
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix stale s2s_cp_stateids IDR entry for async COPY For an async COPY, nfsd4_copy() called nfs4_init_copy_state() before dup_copy_fields(), so the s2s_cp_stateids IDR was pointed at &u->copy->cp_stateid -- memory in the per-rqstp COMPOUND buffer that is reused by the next request. dup_copy_fields() copies only the value into async_copy, so the IDR slot dangled at the transient buffer for the whole background copy. Any IDR walker then dereferences reused request memory: the laundromat reads cs_type from it and, if the bytes look like an expired NFS4_COPYNOTIFY_STID, follows into refcount_dec()/idr_remove()/kfree() on garbage; manage_cpntf_state() has the same exposure via idr_find(). Duplicate the fields first, then register the stateid on the stable async_copy. result->cb_stateid is unchanged.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/14b978e8d05ce018d0afbeb6611833ef91713a02
- git.kernel.org/stable/c/9b4e5e9ba5ae13808b8a6d229d87c54611ba0e7a
- git.kernel.org/stable/c/d0beaee498e11880e72826026db0e9c9890fc114
- git.kernel.org/stable/c/7aa34ea78f74e6ef60c8112635a87fc43d57f6c9
- git.kernel.org/stable/c/bdce362f49410b9def65d76c21f6259cd89696d8
- git.kernel.org/stable/c/745b2edfdd96b8738a94dee450adff4c7d026d5b
- nvd.nist.gov/vuln/detail/CVE-2026-89676
- cve.org/CVERecord?id=CVE-2026-89676
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.