CVE-2026-89692
Description
A flaw was found in the Linux kernel's Network File System (NFS) daemon, nfsd. This vulnerability occurs when a delegation recall operation fails, leaving a critical internal flag uncleared. This prevents subsequent attempts to break the same delegation, leading to a denial of service where file operations or locks can stall indefinitely. This can disrupt access to shared network resources.
Statement
MODERATE impact. A flaw was found in the Linux kernel's Network File System daemon (nfsd) in Red Hat Enterprise Linux 10.2 and OpenShift Container Platform 5.0/5.1. When the NFS server needs to break a delegation, nfsd_break_one_deleg() sets the NFSD4_CALLBACK_RUNNING flag to serialize recall work and queues the recall; if queueing the recall fails, the flag is left permanently set because the only code path that clears it runs from the workqueue that was never queued. Every subsequent attempt to break that same delegation then silently returns without performing the recall, so a conflicting open or lock request on the delegated file stalls indefinitely, resulting in a denial of service against shared NFS resources. Triggering the flaw requires an active NFS delegation plus a failed recall queue attempt on the server, which is why Red Hat rates it moderate (CVSS 5.5, local attack vector with privileges required) rather than the upstream important rating of 7.5, which assumes an unauthenticated network attacker. Earlier Red Hat Enterprise Linux and OpenShift streams are not affected because the vulnerable code, introduced upstream in kernel 6.15, is not present in those kernels. For the affected streams the fix is currently deferred; the residual risk is confined to NFS servers that grant delegations, where a failed recall can leave client file operations or locks blocked until the delegation state is cleared.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 7.5 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
If an adversary can prevent a reference count from reaching zero, then resources might not be released when they are supposed to, thus causing resources to become scarce for future needs.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If an adversary can cause a reference count to reach zero when the resource is still in use, then a resource might be released before it is supposed to be, possibly forcing an error that causes the product to crash or exit out of its current operation.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.