CVE-2026-89711

NFSD: remove flawed WARN_ON_ONCE from nfsd_mode_check

HIGH
8.2
CVSS Score
Published: September 11, 2026 at 07:46 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: NFSD: remove flawed WARN_ON_ONCE from nfsd_mode_check The header for commit e75b23f9e323 ("nfsd: check d_can_lookup in fh_verify of directories") details the assumption that justified adding the WARN_ON_ONCE to nfsd_mode_check(), that assumption is invalid (in the case of NFS reexport). When NFSD exports an NFS filesystem it is very possible for nfsd_mode_check() to encounter a @dentry that doesn't have i_op->lookup (see nfs_fhget()'s NFS_ATTR_FATTR_MOUNTPOINT and NFS_ATTR_FATTR_V4_REFERRAL handling, and d_flags_for_inode()). So remove nfsd_mode_check()'s WARN_ON_ONCE(). The nfserr_notdir return on that branch must stay. It guards the subsequent lookup_one_unlocked() -> __lookup_slow() path, which calls inode->i_op->lookup() with no NULL check, so returning nfserr_notdir is what keeps a client LOOKUP into such a @dentry from dereferencing a NULL method pointer.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.8e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c
Vendor states this is fixed in 2ef131323999539038e306773c8256403834361b (fixed)
Vendor states this is fixed in 7ef182a8fe9c12b0d936880b1e504840639aa009 (fixed)
Vendor states this is fixed in 9f4434893a2783f7384d993cea883aff3fb7a52d (fixed)
Vendor states this is fixed in a275de3bac5635514ca830f2e46b5ff0e66b5c4c (fixed)
Vendor states this is fixed in aa0cf48a448c5a9fe1a1e880899ecd589ce39e6e (fixed)
Vendor states this is fixed in ae251937c6f0237e5b555a5e4ba4595b8206e865 (fixed)
Vendor states this is fixed in b55b4d880bb080fa10eb08ba21a5d8679b8102fe (fixed)
Vendor states this is fixed in e145e8d67a5d41c72d322e7f87ab474d39d9dfb7 (fixed)
Vendor states this is fixed in 4.8 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card