CVE-2026-89708
Description
A flaw was found in the Linux kernel's NFS daemon (nfsd). During the teardown of an NFSv4 session, a race condition can occur where the session's memory is freed while an active callback task still holds a reference to it. This can lead to a use-after-free vulnerability, potentially causing system instability, crashes, or denial of service.
Statement
This vulnerability is rated as Important because an authenticated NFS client can induce kernel memory corruption or a host denial of service, presenting a critical blast radius against the operating system despite requiring precise timing during session destruction. Red Hat Enterprise Linux systems are not exposed in default installations unless the host is explicitly configured and running as an NFS server. The flaw specifically affects the backchannel callback mechanism during NFSv4 session teardown and does not impact systems functioning strictly as NFS clients.
Mitigation
Disable the NFS server service if NFS exports are not required on the system:
# systemctl stop nfs-server.service
# systemctl disable nfs-server.service
If NFS exports are required, restrict network access to port 2049 so only trusted client IP addresses or subnets can access the service:
# firewall-cmd --permanent --zone=public --remove-service=nfs
# firewall-cmd --permanent --zone=public --add-rich-rule='rule family="ipv4" source address="<trusted_ip_or_subnet>" service name="nfs" accept'
# firewall-cmd --reload
Caveats: Stopping nfs-server halts all active file sharing operations. Restricting firewall rules prevents unauthorized clients from connecting to shared volumes.
Warning: Stopping the nfs-server service will terminate active client connections immediately. Reloading firewall rules applies configuration changes immediately.
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 | 7.5 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.