CVE-2026-89711High· 8.2▾ TwilightIn 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 assumptio…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 45.1 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
— → 5.9
none → medium
— → 5.9
none → medium
— → 8.2
none → high
8.2 → 5.9
high → medium
5.9 → 8.2
medium → high
0.2% → 0.6%
Last analysed / modified upstream
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.
Linux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < ae251937c6f0237e5b555a5e4ba4595b8206e865Linux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < e145e8d67a5d41c72d322e7f87ab474d39d9dfb7Linux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < 9f4434893a2783f7384d993cea883aff3fb7a52dLinux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < 2ef131323999539038e306773c8256403834361bLinux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < b55b4d880bb080fa10eb08ba21a5d8679b8102feLinux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < 7ef182a8fe9c12b0d936880b1e504840639aa009Linux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < a275de3bac5635514ca830f2e46b5ff0e66b5c4cLinux >= e75b23f9e323b1e0759619c39d5a9f7a3a5d9d2c < aa0cf48a448c5a9fe1a1e880899ecd589ce39e6eLinux 4.8Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-38564High· 7.8bpf: Add BPF_PROG_TYPE_CGROUP_SKB attach type enforcement in BPF_LINK_CREATE
CVE-2026-99092Noneriscv: patch: fix handling of bpf-jit execmem addresses
CVE-2026-99089NoneASoC: samsung: i2s: enable op_clk in probe to balance runtime PM
CVE-2026-99093Nonemm: don't schedule deferred kernel page table freeing while booting
CVE-2026-99088Nonenet: openvswitch: validate transport header presence in set_ipv6_addr
CVE-2026-99090Nonedrm/amdgpu: serialize vblank counter reads against GPU reset