CVE-2025-21795: NFSD: fix hang in nfsd4_shutdown_callback
In the Linux kernel, the following vulnerability has been resolved:
NFSD: fix hang in nfsd4_shutdown_callback
If nfs4_client is in courtesy state then there is no point to send
the callback. This causes nfsd4_shutdown_callback to hang since
cl_cb_inflight is not 0. This hang lasts about 15 minutes until TCP
notifies NFSD that the connection was dropped.
This patch modifies nfsd4_run_cb_work to skip the RPC call if
nfs4_client is in courtesy state.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux NFSv4 server can delay callback shutdown for roughly 15 minutes when a client is in courtesy state. The primary impact is reduced availability; the supplied CVSS assessment is 7.5. Systems not providing NFS services are unlikely to be exposed through this component.
Executive priority
Treat this as a high-priority availability issue for business-critical NFSv4 servers, especially shared storage supporting production workloads. Patch through normal emergency or accelerated maintenance processes after confirming exposure. Lower the priority for systems where NFSD is absent or disabled.
Technical view
NFSD may attempt a callback for an NFSv4 client in courtesy state, leaving cl_cb_inflight nonzero and hanging nfsd4_shutdown_callback until TCP reports the dropped connection. The kernel fix changes nfsd4_run_cb_work to skip that RPC call. No confidentiality or integrity impact is identified in the supplied CVSS vector.
Likely exposure
Exposure is concentrated in Linux systems running the NFSv4 server on affected kernels. The bundle lists several affected upstream releases, but distribution kernels may contain backported fixes despite older version numbers. Confirm package status through the relevant vendor advisory rather than relying only on uname output.
Exploitation context
The supplied record rates the issue as network-accessible, low-complexity, unauthenticated, and availability-only. However, it provides no public exploit evidence or precise attacker-controlled trigger sequence. The CVE is not listed as KEV in the bundle, so active exploitation is not established.
Researcher notes
The described failure is a shutdown-path hang caused by callback accounting remaining active for a courtesy-state client. The fix avoids initiating the RPC in that state. Source evidence supports an approximately 15-minute delay, but does not establish repeatable malicious exploitation, service-wide outage scope, or observed attacks.
Mitigation direction
Install the vendor kernel update containing the NFSD callback fix.
Prioritize internet-facing or broadly reachable NFSv4 servers.
Restrict NFS access to required clients and trusted network segments.
If patching is delayed, consult vendor guidance for supported temporary mitigations.
Validation and detection
Inventory systems running or configured to run the Linux NFS server.
Compare installed kernel packages with distribution and appliance vendor advisories.
Confirm the deployed kernel includes the applicable stable fix or vendor backport.
Review NFS service logs and operations for callback-shutdown delays or prolonged hangs.
After updating, verify the corrected kernel is running following any required reboot.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21795 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
13Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.