Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-89675: nfsd: fix UAF in async copy cancel and shutdown

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 62c0f6eaf050bb9284c1f9cac6ed1770092e6b95, 9031493ef7369d5c59c4bacc96f0c85965f09a98, a385cf5e016b748babf94cc664e43a26e17db117; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 62c0f6eaf050bb9284c1f9cac6ed1770092e6b95, 9031493ef7369d5c59c4bacc96f0c85965f09a98, a385cf5e016b748babf94cc664e43a26e17db117; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 19, 2026
EPSS
0.4% · 38th percentile
CWE
—

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-89675

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.20affected
    • e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before 9031493ef7369d5c59c4bacc96f0c85965f09a98affected · git
    • e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before a385cf5e016b748babf94cc664e43a26e17db117affected · git
    • e0639dc5805a9d4faaa2c07ad98fa853b9529dd3 and later · before 62c0f6eaf050bb9284c1f9cac6ed1770092e6b95affected · git
    • before 4.20not affected · semver
    • 6.18.51 and later · up to and including 6.18.*not affected · semver
    • 7.2.4 and later · up to and including 7.2.*not affected · semver
    • 7.3 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.64.1.el10_26.12.0-211.64.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-89673Sep 11, 2026 · nfsd: fix XDR padding calculation in ff_encode_getdeviceinfo
    0Monitor
  • ← EarlierCVE-2026-89674Sep 11, 2026 · nfsd: fix XDR length calculation in nfsd4_ff_encode_layoutget
    39Monitor
  • Later →CVE-2026-89676Sep 11, 2026 · nfsd: fix stale s2s_cp_stateids IDR entry for async COPY
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux62c0f6eaf050bb9284c1f9cac6ed1770092e6b95Vendor (CNA)
Linux Linux9031493ef7369d5c59c4bacc96f0c85965f09a98Vendor (CNA)
Linux Linuxa385cf5e016b748babf94cc664e43a26e17db117Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.64.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux7.2.6-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-211.64.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-modules-internal0:6.12.0-211.64.1.el10_2 · Red Hat:shadow_migration_toolkit:10::el10Package registry (OSV)
rocky linux:kernel0:6.12.0-211.64.1.el10_2 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records