CVE-2026-99368 in Linuxinfo

Summary

by MITRE • 11/19/2026

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.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The vulnerability resides within the Network File System server implementation in the Linux kernel, specifically affecting the delegation reaper mechanism during NFSv4 operations. The core technical flaw involves a protocol version mismatch where the server incorrectly attempts to utilize an operation that is not supported by older client versions. Specifically, the deleg_reaper function iterates through all active clients holding file system delegations and issues a CB_RECALL_ANY callback request. This particular callback type was introduced in NFSv4.1 as part of the protocol enhancements for handling delegation recalls more efficiently. However, when this operation is directed at an NFSv4.0 client, it violates the specification because NFSv4.0 clients are designed to accept only CB_GETATTR and CB_RECALL callbacks. Consequently, the client responds with an OP_ILLEGAL error code indicating that the requested operation number is not recognized or supported by its implementation of the callback service protocol.

The immediate operational impact stems from how the server handles this illegal response within its internal state machine. Upon receiving the unexpected opcode, the decoder maps it to a generic input-output error status, which triggers nfsd4_cb_done to mark the client's callback channel as down. This action is critical because the subsequent logic in nfsd4_run_cb_work only sets the NFSD4_CB_UP flag for clients with a minor version greater than zero, effectively excluding NFSv4.0 from being marked as having an active callback path after such an error. Furthermore, the recovery mechanism relies on specific handshake sequences that do not properly re-establish the channel state for these older clients under normal circumstances. As a result, once the delegation reaper visits an NFSv4.0 client and triggers this failure sequence, the callback channel remains permanently marked as down until the client explicitly re-establishes its client identifier through a renewal process.

This persistent state corruption leads to significant service degradation for affected systems. While the callback channel is marked down, any subsequent RENEW requests from the NFSv4.0 client are rejected with an error code indicating that the callback path is down. This creates a cascading failure where the server refuses further delegation grants because nfsd4_cb_channel_good returns false due to the erroneous state flag. Essentially, the vulnerability causes a denial of service for file system operations requiring delegations on NFSv4.0 clients connected to vulnerable servers. The client loses its ability to cache data locally and optimize I/O performance, forcing it into less efficient direct access modes or potentially causing application timeouts if delegation is critical to its operation model.

From a classification perspective, this issue aligns with CWE-20 Improper Input Validation as the server fails to validate the protocol version compatibility before issuing an unsupported command. It also relates to CWE-693 Protection Mechanism Failure because the internal state management logic incorrectly transitions the callback channel to a failed state without providing a valid recovery path for older protocol versions. In terms of adversary behavior, this could be leveraged in a Denial of Service scenario where an attacker might exploit similar version mismatches or trigger reaper cycles to disrupt file sharing services, mapping loosely to ATT&CK techniques involving resource exhaustion or service disruption within networked storage environments.

The resolution implemented by the Linux kernel maintainers addresses this flaw by modifying the delegation reaper logic to explicitly skip clients operating at minor version zero of NFSv4. By filtering out these older protocol versions before attempting to send CB_RECALL_ANY, the server prevents the generation of illegal operations that trigger the erroneous state transitions. This fix ensures that only compatible clients receive callbacks they can process correctly, thereby maintaining the integrity of the callback channel status and preventing the cascading failures described above. Administrators should ensure their kernel is updated with this patch to restore proper delegation handling for mixed-version NFS environments and prevent unintended service interruptions for legacy client systems relying on NFSv4.0 protocols.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00201

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!