CVE-2026-89663
Received Received - Intake

Use-After-Free in Linux Kernel NFSd Copy-Notify State Handling

Vulnerability report for CVE-2026-89663, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-11

Last updated on: 2026-09-14

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: revoke copy-notify stateids before dropping their reference Copy-notify stateids live in the s2s_cp_stateids IDR and on their parent stid's sc_cp_list, pinned by a single membership reference. _free_cpntf_state_locked() only unlinks an entry once its refcount reaches zero, so any revoke path that runs while a concurrent find_cpntf_state()/manage_cpntf_state() holder has elevated cs_count drops the reference without unlinking, leaving the entry discoverable with its membership reference already consumed. A second revoke or a laundromat tick then frees it while the reader still holds the pointer -- a KASAN-detectable use-after-free at the reader's nfs4_put_cpntf_state(). This affected all three revoke paths: - The parent-stid drain (nfs4_free_cpntf_statelist()) repeatedly called _free_cpntf_state_locked() on the first list entry; a holder that had bumped cs_count made it return early, so the next iteration re-decremented and burned the holder's reference. - OFFLOAD_CANCEL (manage_cpntf_state()) and laundromat expiry likewise used _free_cpntf_state_locked() and could drop 2->1 without unlinking. Add revoke_cpntf_state_locked(), which unhashes the entry from the IDR and sc_cp_list first (deferring the final free to any holder), and use it from all three revoke paths. The drain now walks with list_for_each_entry_safe() and revokes each entry unconditionally, so it terminates in one pass per entry regardless of cs_count. The unhash is gated on !list_empty(&cps->cp_list); the idr_remove() gate matters because idr_alloc_cyclic() may have recycled the so_id by then. Keep _free_cpntf_state_locked() for the reference-holder put path only, where a concurrent revoke may already have unlinked the entry (its list_del_init() then a no-op).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-14
Generated
2026-10-02
AI Q&A
2026-09-12
EPSS Evaluated
2026-10-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a use-after-free vulnerability in the Linux kernel's NFS server (nfsd) related to copy-notify stateids. The issue occurs when revoking stateids while another process holds a reference. The revoke operation may drop the reference without properly unlinking the stateid, leaving it accessible. Later operations can then free the stateid while the original holder still has a pointer, causing a use-after-free detected by KASAN.

Detection Guidance

This vulnerability is specific to the Linux kernel's NFS (Network File System) implementation. Detection requires checking the kernel version and NFS-related components. Use commands like 'uname -a' to check the kernel version and 'lsmod | grep nfsd' to verify if NFS server modules are loaded. If your kernel version is affected and NFS is in use, further investigation is needed.

Impact Analysis

This vulnerability could allow an attacker to cause a kernel crash or execute arbitrary code in the kernel context by exploiting the use-after-free condition. This would lead to system instability, potential denial of service, or unauthorized access depending on the attacker's capabilities and system configuration.

Compliance Impact

This vulnerability is a use-after-free issue in the Linux kernel's NFS server implementation. It does not directly relate to data protection, privacy, or security controls required by GDPR or HIPAA. The impact is limited to kernel stability and potential denial-of-service conditions rather than compliance violations.

Mitigation Strategies

Apply the latest kernel patches or updates that address this vulnerability. If immediate patching is not possible, consider disabling NFS server functionality temporarily until the patch is applied. Monitor vendor advisories for kernel updates.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-89663. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart