All reports
Medium

kernel: nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-46690

Probability of exploitation in the next 30 days: 0.40%

FIRST EPSS · 2026-11-19

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease It is not safe to dereference fl->c.flc_owner without first confirming fl->fl_lmops is the expected manager. nfsd4_deleg_getattr_conflict() tests fl_lmops but largely ignores the result and assumes that flc_owner is an nfs4_delegation anyway. This is wrong. With this patch we restore the "!= &nfsd_lease_mng_ops" case to behave as it did before the change mentioned below. This is the same as the current code, but without any reference to a possible delegation.

A flaw was found in the Linux kernel's Network File System Daemon (nfsd) component. An issue in the nfsd4_deleg_getattr_conflict function, specifically related to handling third-party leases, allows for unsafe dereferencing of a pointer. This could lead to a local attacker causing a denial of service (DoS) by triggering an unexpected state in the kernel.