CVE-2026-99368
NFSD: Do not send CB_RECALL_ANY to NFSv4.0 clients
Description
In the Linux kernel, the following vulnerability has been resolved: NFSD: Do not send CB_RECALL_ANY to NFSv4.0 clients deleg_reaper() sends CB_RECALL_ANY to every ACTIVE client holding delegations, but CB_RECALL_ANY is an NFSv4.1 operation. An NFSv4.0 client's callback service accepts only CB_GETATTR and CB_RECALL, so it replies OP_ILLEGAL. The decoder maps the unexpected opnum to -EIO, and nfsd4_cb_done() marks the client's callback channel down. Nothing brings the channel back. nfsd4_run_cb_work() sets NFSD4_CB_UP only for a minor version above zero, and the only nfsd4_probe_callback() call site an NFSv4.0 client reaches is nfsd4_setclientid_confirm(). One visit from the reaper therefore leaves the channel marked down until the client re-establishes its clientid. RENEW then returns NFS4ERR_CB_PATH_DOWN for as long as the client holds delegations. nfsd4_cb_channel_good() stops returning true, so the client is granted no further delegations. Skip clients at minor version zero.
INFO
Published Date :
Nov. 19, 2026, 2:22 p.m.
Last Modified :
Nov. 19, 2026, 2:22 p.m.
Remotely Exploit :
No
Source :
Linux
Solution
- Update the Linux kernel to include the fix.
- Ensure the delegation reaper handles NFSv4.0 clients correctly.
- Verify callback channels remain operational for NFSv4.0 clients.
- Test client reconnection after the patch is applied.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-99368 vulnerability anywhere in the article.