CVE-2026-89676: nfsd: fix stale s2s_cp_stateids IDR entry for async COPY

Published Sep 11, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

nfsd: fix stale s2scpstateids IDR entry for async COPY

For an async COPY, nfsd4copy() called nfs4initcopystate() before dupcopyfields(), so the s2scpstateids IDR was pointed at &u->copy->cpstateid -- memory in the per-rqstp COMPOUND buffer that is reused by the next request. dupcopyfields() copies only the value into asynccopy, 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 cstype from it and, if the bytes look like an expired NFS4COPYNOTIFYSTID, follows into refcountdec()/idrremove()/kfree() on garbage; managecpntfstate() has the same exposure via idrfind().

Duplicate the fields first, then register the stateid on the stable asynccopy. result->cbstateid is unchanged.

Affected Software

1 affected component
Linux Linux kernel

Event History

Sep 11, 2026
CVE Published
via MITRE·07:46 PM
Data Sourced
via MITRE·07:46 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems running the Linux kernel NFS server component (nfsd) are exposed when they handle asynchronous NFS COPY operations. The issue is in server-side state tracking for background copies.

2

What must occur for the vulnerable code path to be reached?

An asynchronous COPY request must cause nfsd to create copy state. Exposure persists while the background copy is active because the state IDR can retain a pointer to reused per-request memory.

3

What could trigger the unsafe dereference after the COPY request?

An IDR walker can dereference the stale entry. The described paths include the laundromat and manage_cpntf_state(); if reused bytes resemble an expired NFS4_COPYNOTIFY_STID, the kernel may operate on garbage through refcount decrement, IDR removal, and free operations.

4

What is the remediation?

Apply a kernel update containing the fix that duplicates COPY fields before registering the stateid, so the IDR points to stable async_copy storage rather than the transient request buffer. The provided stable-kernel references identify commits containing the correction.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203