Answer in brief
CVE-2026-89676 records a Critical severity (CVSS 9.8) vulnerability in nfsd: fix stale s2s_cp_stateids IDR entry for async COPY. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <9b4e5e9ba5ae13808b8a6d229d87c54611ba0e7a || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <14b978e8d05ce018d0afbeb6611833ef91713a02 || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <d0beaee498e11880e72826026db0e9c9890fc114 | 9b4e5e9ba5ae13808b8a6d229d87c54611ba0e7a, 14b978e8d05ce018d0afbeb6611833ef91713a02, d0beaee498e11880e72826026db0e9c9890fc114 |
| Linux/Linuxgeneric | 4.20 | Not reported |
| Linux/Linuxgeneric | >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <7aa34ea78f74e6ef60c8112635a87fc43d57f6c9 || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <9b4e5e9ba5ae13808b8a6d229d87c54611ba0e7a || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <14b978e8d05ce018d0afbeb6611833ef91713a02 || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <d0beaee498e11880e72826026db0e9c9890fc114 | 7aa34ea78f74e6ef60c8112635a87fc43d57f6c9, 9b4e5e9ba5ae13808b8a6d229d87c54611ba0e7a, 14b978e8d05ce018d0afbeb6611833ef91713a02, d0beaee498e11880e72826026db0e9c9890fc114 |
| Linux/Linuxgeneric | >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <bdce362f49410b9def65d76c21f6259cd89696d8 || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <7aa34ea78f74e6ef60c8112635a87fc43d57f6c9 || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <9b4e5e9ba5ae13808b8a6d229d87c54611ba0e7a || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <14b978e8d05ce018d0afbeb6611833ef91713a02 || >=e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <d0beaee498e11880e72826026db0e9c9890fc114 | bdce362f49410b9def65d76c21f6259cd89696d8, 7aa34ea78f74e6ef60c8112635a87fc43d57f6c9, 9b4e5e9ba5ae13808b8a6d229d87c54611ba0e7a, 14b978e8d05ce018d0afbeb6611833ef91713a02, d0beaee498e11880e72826026db0e9c9890fc114 |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
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.
Quoted source text, attributed separately from HOL analysis.