Menu

Star on GitHub · 3.5k

CVE-2026-89712

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock nfsd4_ssc_expire_umount() walks nn->nfsd_ssc_mount_list with…

Published Sep 11, 2026EPSS 0.71%

Overview

CVE-2026-89712 is a critical-severity vulnerability. It was published on September 11, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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

NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock

nfsd4_ssc_expire_umount() walks nn->nfsd_ssc_mount_list with

list_for_each_entry_safe(ni, tmp, ...). For each expired entry it

sets nsui_busy = true, drops nfsd_ssc_lock to run mntput() on the

source vfsmount, then reacquires the lock to list_del + kfree the

entry and continue iterating via the macro's saved tmp pointer.

The nsui_busy flag protects the current ni from concurrent

nfsd4_ssc_setup_dul() finders during the lock-drop window, but it

does not pin tmp. Another nfsd RPC thread that fails its source-

server mount and reaches nfsd4_ssc_cancel_dul() will, during that

same window, take nfsd_ssc_lock, list_del + kfree its own ssc_umount

item, and release the lock. If that item is the saved tmp of the

expire walk, the next iteration dereferences a freed

nfsd4_ssc_umount_item.

Restart the walk from the head after the mntput() unlock window so

no

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-89712?

CVE-2026-89712 is a critical-severity vulnerability. It was published on September 11, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2026-89712?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-89712?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-89712?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-89712 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all
CyberStrike v2 is here — more intelligence, greater reach