CVE-2026-89708
Received Received - Intake

Use-After-Free in Linux Kernel NFS Server

Vulnerability report for CVE-2026-89708, 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-21

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: RCU-protect cl_cb_session to fix use-after-free on session teardown After a DESTROY_SESSION the per-session teardown path can free a session while rpciod still holds an inflight callback rpc_task that dereferences clp->cl_cb_session. nfsd4_probe_callback_sync() flushes cl_callback_wq, but once nfsd4_run_cb_work() has called rpc_call_async() the rpc_task lives on rpciod; flushing the workqueue does not wait for it. rpc_shutdown_client() does drain rpciod tasks, but uses a 1-second wait_event_timeout β€” tasks stuck in rpc_delay() (e.g. 2-second NFS4ERR_DELAY retries) can outlive the drain. destroy path rpciod ------------ ------ unhash_session(ses) nfsd4_probe_callback_sync(clp) flush_workqueue(cl_callback_wq) /* returns; rpc_task still live */ nfsd4_put_session_locked(ses) free_session(ses) -> kfree(ses) nfsd4_cb_sequence_done() reads cb_clp->cl_cb_session /* freed slab */ A second window exists in nfsd4_process_cb_update(). When __nfsd4_find_backchannel() returns NULL because unhash_session() has already removed the destroyed session from cl_sessions, setup_callback_client() takes the v4.1 early return so clp->cl_cb_session = ses never fires and the field retains a pointer to the about-to-be-freed session. Fix both by converting cl_cb_session to an RCU-protected pointer: - Move the cl_cb_session = ses assignment in setup_callback_client() to after rpc_create() succeeds, so it is only published when a working backchannel exists. Clear cl_cb_session on the error return in nfsd4_process_cb_update(). Both stores use rcu_assign_pointer(). - Annotate cl_cb_session with __rcu. All rpciod-side readers use rcu_read_lock()/rcu_dereference() and check for NULL, bailing to the appropriate error or requeue path: encode_cb_sequence4args(), decode_cb_sequence4resok(), nfsd41_cb_get_slot(), nfsd41_cb_release_slot(), nfsd4_cb_prepare(), and nfsd4_cb_sequence_done(). - Switch __free_session() from kfree() to kfree_rcu() so the session slab is not reclaimed until after an RCU grace period, guaranteeing that rpciod readers inside rcu_read_lock() never dereference freed memory. - Pass the session pointer to the nfsd_cb_seq_status and nfsd_cb_free_slot tracepoints instead of having them re-read cl_cb_session. - nfsd4_cb_prepare() calls rpc_exit() when the session is NULL, routing through the done/release path to requeue the callback.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-21
Generated
2026-10-02
AI Q&A
2026-09-12
EPSS Evaluated
2026-09-29
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). It occurs when a session is destroyed while an RPC callback task is still running in the background. The callback task may try to access a session pointer that has already been freed, leading to memory corruption or crashes.

Detection Guidance

This vulnerability is specific to the Linux kernel's NFS server (nfsd) and involves a use-after-free issue in session teardown. Detection requires checking kernel logs for NFS-related errors or crashes, particularly during session destruction or callback processing. Monitor logs for messages related to nfsd, rpc tasks, or memory corruption. No direct commands are provided in the context, but kernel logs and crash dumps may reveal the issue.

Impact Analysis

If exploited, this could cause system instability, crashes, or potential privilege escalation on systems running vulnerable NFS server configurations. It primarily affects systems using NFSv4.1 or later with callback functionality enabled.

Compliance Impact

This vulnerability involves a use-after-free issue in the Linux kernel's NFS server (nfsd) related to session teardown and callback handling. It does not directly impact compliance with standards like GDPR or HIPAA, as those focus on data protection, privacy, and security controls rather than kernel-level memory management flaws.

Mitigation Strategies

Apply the kernel patch that resolves this issue by updating to a version containing the fix. The patch involves RCU protection for cl_cb_session and changes to session teardown logic. If immediate patching is not possible, consider disabling NFSv4.1 callbacks as a temporary workaround, but this may impact functionality. Monitor vendor advisories for kernel updates addressing CVE-2026-89708.

Chat Assistant

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

EPSS Chart