Skip to main content

Linux Kernel EUVDEUVD-2026-76587

| CVE-2026-89675 CRITICAL
2026-09-11 Linux GHSA-gw8w-5rwc-5ffx
Critical
Disputed · 9.8 Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to NFSv4.2 server
  2. Delivery
    Initiate async server-side COPY
  3. Exploit
    Send OFFLOAD_CANCEL racing copy kthread
  4. Execution
    Trigger double-put/UAF of copy files
  5. Impact
    Kernel oops / denial of service

Vulnerability Assessment

Exploitation Conditions

Requires the target to be an in-kernel Linux NFS server actively serving NFSv4.2 with server-side copy offload in use. The attacker-driven path needs an authenticated NFSv4.2 client that can initiate an asynchronous COPY and then an OFFLOAD_CANCEL, and must win a race against the server's copy kthread / laundromat reaper. The shutdown and per-superblock cancel paths (nfsd4_shutdown_copy, nfsd4_cancel_copy_by_sb) require local administrative actions such as stopping the NFS service or unmounting/removing the exported filesystem while a copy is in flight. Limiting factors: exploitation is a timing-dependent race (not deterministic), depends on the non-default use of NFSv4.2 server-side copy, and requires either an authenticated client or local admin activity - it is not unauthenticated-against-default-config despite the CVSS AV:N/PR:N vector.

Impact

The published CVSS 3.1 vector (9.8, AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:H) substantially overstates real-world risk. This is a race-condition UAF in server-side copy teardown, so exploitation is timing-dependent (AC:H, not AC:L) and requires an authenticated NFSv4.2 client to initiate a COPY and OFFLOAD_CANCEL, or local administrative action to shut down/unmount the export - meaning PR:N is inaccurate (should be PR:L, with several paths effectively AV:L/local-admin). The realistic impact is availability (kernel crash/oops on the NFS server), not confidentiality or integrity, so C:H/I:H is not supported by the description. Corroborating signals point to low practical urgency: EPSS is 0.17% (6th percentile), the CVE is not in CISA KEV, and no POC is referenced. The 'Information Disclosure' tag is a mislabel - this is a memory-safety/DoS bug. Net assessment: a legitimate kernel memory-safety defect worth patching on NFالسv4.2 servers, but not the internet-facing, trivially automatable critical the 9.8 implies; prioritize below unauthenticated RCE and KEV-listed issues.

Exploit ScenarioDerived

An authenticated NFSv4.2 client on a network-reachable NFS server starts a large asynchronous server-side COPY, then issues an OFFLOAD_CANCEL while the copy kthread is still running, repeatedly, to win the teardown race; alternatively, an administrator's export shutdown or filesystem unmount races an in-flight copy. The double-put and use-after-free of the nfsd_file/copy objects crashes or corrupts memory in the server kernel, causing denial of service. No public exploit is identified at time of analysis, and the race timing (AC:H) makes reliable triggering difficult.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 13, 2026

A use-after-free in the Linux kernel NFSD server's asynchronous server-side copy (NFSv4.2 COPY offload) lets teardown paths race the copy kthread, corrupting or freeing the copy object early. When an OFFLOAD_CANCEL request, an nfsd export/superblock shutdown, or a per-filesystem cancel runs concurrently with the reaping copy kthread, nfsd_file structures (nf_src/nf_dst) are double-put and freed, the STOPPED flag is set before final dereferences, and the copy_task/callback are used after free - causing NULL derefs, double frees, and UAF that can crash an NFSv4.2-serving host. Fixed in stable kernels 6.18.51, 7.2.4, and 7.3-rc1; no public exploit identified at time of analysis and EPSS is low (0.17%).

RemediationAI

Vendor-released patch: upgrade to Linux kernel 6.18.51, 7.2.4, or 7.3-rc1 (or your distribution's backported build carrying the referenced stable commits 9031493ef736, a385cf5e016b, and 62c0f6eaf050). Apply the fix via git.kernel.org/stable and rebuild/reboot, or install the vendor kernel update from your distribution. If immediate patching is not possible on an NFSv4.2 server, the most direct compensating control is to disable server-side copy offload by not advertising/using NFSv4.2 (export with NFSv4.0/4.1 or vers=4.1 constraints) - trade-off: clients lose efficient server-side COPY and fall back to read/write copies. Additional hardening: restrict NFS export access to trusted client networks and authenticated principals (e.g., krb5) to limit who can issue COPY/OFFLOAD_CANCEL, and avoid concurrent export teardown/unmount while copies are active; these reduce but do not eliminate the race window. Monitor for kernel oops/UAF signatures in NFSD during copy cancellation as a detection measure.

Affected VersionsENISA

Linux 4.20
Linux e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <9031493ef7369d5c59c4bacc96f0c85965f09a98
Linux e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <62c0f6eaf050bb9284c1f9cac6ed1770092e6b95
Linux patch: 7.3-rc1
Linux patch: 7.2.4
Linux e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 <a385cf5e016b748babf94cc664e43a26e17db117
Linux patch: 6.18.51
Linux patch: 0

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is in the Linux kernel NFSD subsystem (fs/nfsd), specifically the NFSv4.2 asynchronous server-side copy feature ('inter/intra-server copy offload'), where the server spawns a one-shot kthread to perform a COPY and reports completion via a CB_OFFLOAD callback. The root cause is CWE-416 (use-after-free), reported here despite the input CWE being 'N/A'. Multiple lifetime bugs combine: find_async_copy() incremented copy->refcount but left the copy linked on clp->async_copies, so the laundromat reaper's cleanup_async_copy()/release_copy_files() could run concurrently with cancel/shutdown callers, each putting and NULLing the shared nfsd_file pointers without a common lock; nfsd4_do_async_copy() set NFSD4_COPY_F_STOPPED before its last uses of copy->nf_dst, causing nfsd4_stop_copy() to skip kthread_stop() while the kthread still dereferenced freed memory; copy->copy_task was never pinned with get_task_struct(), so a self-reaping kthread could leave kthread_stop() touching a freed task_struct; and the embedded co_cb callback held a reference only on the client, not the copy, so a concurrent teardown could free the copy mid-CB_OFFLOAD. The CPE (cpe:2.3:a:linux:linux) confirms this is the mainline Linux kernel. The fix reworks the whole teardown lifetime: unlink under async_lock, drop the list reference via nfs4_put_copy() after nfsd4_stop_copy(), free s2s_cp_stateids explicitly, give the kthread its own reference, pin the task_struct, set STOPPED only in nfsd4_stop_copy(), reference the copy in nfsd4_send_cb_offload(), and use smp_load_acquire() on cp_clp.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Sources disagree (Medium–Critical)
Vendor (Linux) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 5.3 MEDIUM

Authenticated NFSv4.2 client wins a teardown race (PR:L, AC:H) to crash the server kernel; impact is availability only, no confidentiality or integrity.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE 6.4 MEDIUM
AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
Red Hat 7.0 HIGH

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 13, 2026 - 07:22 NVD
9.8 (CRITICAL)
Patch available
Sep 11, 2026 - 21:18 EUVD
CVE Published
Sep 11, 2026 - 19:45 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 11, 2026 - 19:45 cve.org
CRITICAL 9.8

DescriptionCVE.org

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

nfsd: fix UAF in async copy cancel and shutdown

An async copy could be freed or used after free while a teardown caller (OFFLOAD_CANCEL, nfsd4_shutdown_copy, nfsd4_cancel_copy_by_sb) raced the copy kthread:

  • find_async_copy() bumped copy->refcount but left the copy on

clp->async_copies, so the reaper's cleanup_async_copy() could run release_copy_files() concurrently with a cancel/shutdown caller. Both put and NULL nf_src/nf_dst without a common lock, double-putting the nfsd_file and freeing it early.

  • nfsd4_do_async_copy() set NFSD4_COPY_F_STOPPED before its final uses

of the copy (nfsd_update_cmtime_attr() on copy->nf_dst, nfsd4_send_cb_offload()). nfsd4_stop_copy() treats a set STOPPED bit as "kthread done, skip kthread_stop()", so a teardown caller ran release_copy_files() -- which puts and NULLs nf_dst -- while the kthread still dereferenced it (NULL/UAF).

  • copy->copy_task was never pinned. The one-shot kthread self-reaps on

return, so kthread_stop()'s get_task_struct() could touch a freed task_struct.

  • co_cb is embedded in the copy, but nfsd4_send_cb_offload() held a

reference only on the client, so a concurrent teardown could free the copy while the CB_OFFLOAD callback was in flight.

Fix the teardown lifetime as a whole:

  • find_async_copy() unlinks the copy (clear cp_clp, list_del_init)

under async_lock; the cancel, shutdown, and sb-cancel paths drop the list-membership reference via nfs4_put_copy() after nfsd4_stop_copy(). Drop the now-redundant list_del fixup from cleanup_async_copy().

  • Because unlinking hides the copy from the reaper, its

cleanup_async_copy() can no longer remove the copy's s2s_cp_stateids entry; the cancel/shutdown/sb-cancel paths now call nfs4_free_copy_state() themselves (while cp_clp is still valid) so the entry does not dangle at freed memory for the laundromat and manage_cpntf_state() to dereference.

  • Give the kthread its own reference, taken in nfsd4_copy() before

wake_up_process() and dropped at the end of nfsd4_do_async_copy(); call wake_up_process() before list_add().

  • Pin the task_struct with get_task_struct() in nfsd4_copy(), released

in nfs4_put_copy(), so kthread_stop() is safe whenever the kthread exits. Set NFSD4_COPY_F_STOPPED only in nfsd4_stop_copy(), which now always kthread_stop()s before release_copy_files(); completion is still reported via NFSD4_COPY_F_COMPLETED, so nfsd4_has_active_async_copies() is unaffected. Each teardown caller removes the copy from clp->async_copies first, so kthread_stop() runs exactly once.

  • Take a copy reference in nfsd4_send_cb_offload(), dropped in

nfsd4_cb_offload_release(). The kthread still holds its own reference there, so the refcount_inc() cannot race the final free.

  • Read cp_clp with smp_load_acquire() to pair with the unordered

set_bit()/clear_bit() writers (Documentation/atomic_bitops.rst).

Executive ViewAI

Why It Matters

NFS servers running affected Linux kernels face denial-of-service risk from a use-after-free vulnerability in NFSv4.2 file copy operations that could crash the storage server during concurrent copy requests. Organizations using NFS for critical file sharing should prioritize patching to prevent service interruptions that cascade to dependent applications and workloads.

Business Impact: High
Compensating Controls

Apply vendor patch: Linux kernel 6.18.51, 7.2.4, or later stable 7.x releases. If patching cannot be expedited, disable COPY offload on NFSv4.2 exports as a temporary compensating control, though this may impact applications relying on server-side copy performance.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Ubiquitous
Linux kernel; NFSD is a standard in-kernel server, though NFSv4.2 copy is optional
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy