CVE-2026-90151: NFSv4: remove callback IDR entry on client allocation failure
In the Linux kernel, the following vulnerability has been resolved:
NFSv4: remove callback IDR entry on client allocation failure
nfs4allocclient() allocates an NFSv4.0 callback identifier before it finishes setting up the client. If any later initialization step fails, the error path frees the nfsclient directly with nfsfreeclient(). That bypasses nfsputclient(), which is where the callback IDR entry is removed during normal teardown.
A failed allocation can therefore leave cbidentidr pointing at a freed nfsclient. A later NFSv4.0 callback lookup by cbident would find the stale pointer and take a reference to it.
Make the callback IDR removal helper callable by the allocation failure path, and remove the callback identifier before freeing the client.
This was found by a local static-analysis checker for publish-before-free lifetime bugs and confirmed by manual inspection.
Affected Software
Event History
Frequently Asked Questions
What conditions are required for the stale pointer to be used?
An NFSv4.0 client setup must fail after its callback identifier has been allocated, leaving the callback IDR entry behind. A later NFSv4.0 callback lookup using that callback identifier can then locate the stale pointer and attempt to take a reference to the freed nfs_client.
Is this limited to a particular NFS protocol version?
The described vulnerable path and subsequent callback lookup are specifically for NFSv4.0. The provided information does not establish impact for other NFS versions.
How can administrators determine whether the vulnerable condition may have occurred?
The issue requires a failed NFSv4.0 client allocation after callback-ID allocation. The provided information does not identify a log message, configuration check, or runtime indicator that confirms a stale callback IDR entry is present.