Vulnerability · Published Jan 13, 2026 · Assigned by Linux
CVE-2025-71090nfsd: fix nfsd_file reference leak in nfsd4_add_rdaccess_to_wrdeleg()
High 7.5
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix nfsd_file reference leak in nfsd4_add_rdaccess_to_wrdeleg() nfsd4_add_rdaccess_to_wrdeleg() unconditionally overwrites fp->fi_fds[O_RDONLY] with a newly acquired nfsd_file. However, if the client already has a SHARE_ACCESS_READ open from a previous OPEN operation, this action overwrites the existing pointer without releasing its reference, orphaning the previous reference. Additionally, the function originally stored the same nfsd_file pointer in both fp->fi_fds[O_RDONLY] and fp->fi_rdeleg_file with only a single reference. When put_deleg_file() runs, it clears fi_rdeleg_file and calls nfs4_file_put_access() to release the file. However, nfs4_file_put_access() only releases fi_fds[O_RDONLY] when the fi_access[O_RDONLY] counter drops to zero. If another READ open exists on the file, the counter remains elevated and the nfsd_file reference from the delegation is never released. This potentially causes open conflicts on that file. Then, on server shutdown, these leaks cause __nfsd_file_cache_purge() to encounter files with an elevated reference count that cannot be cleaned up, ultimately triggering a BUG() in kmem_cache_destroy() because there are still nfsd_file objects allocated in that cache.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:14 | linux | 6.18.5-1 | DEBIAN-CVE-2025-71090 |
| Ubuntu:25.10 | linux | 6.17.0-29.29 | USN-8277-1 |
| Ubuntu:25.10 | linux | 6.17.0-29.29 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1015.15 | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-aws | 6.17.0-1015.15 | USN-8277-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1017.17~24.04.1 | USN-8374-1 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | 6.17.0-1017.17~24.04.1 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1015.15 | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-azure | 6.17.0-1015.15 | USN-8310-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1015.15~24.04.1 | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1015.15~24.04.1 | USN-8310-1 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1018.19 | USN-8374-1 |
| Ubuntu:25.10 | linux-gcp | 6.17.0-1018.19 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1018.19~24.04.1 | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1018.19~24.04.1 | USN-8374-1 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-29.29~24.04.1 | USN-8277-1 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-29.29~24.04.1 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1026.26 | USN-8508-1 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1026.26 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1023.23 | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1023.23 | USN-8277-1 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1014.14 | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-oracle | 6.17.0-1014.14 | USN-8277-1 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1014.14~24.04.1 | USN-8277-2 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1014.14~24.04.1 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1017.17 | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-raspi | 6.17.0-1017.17 | USN-8277-1 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1013.15 | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-realtime | 6.17.0-1013.15 | USN-8277-1 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:25.10 | linux-riscv | 6.17.0-29.29.1 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | 6.17.0-29.29.1~24.04.1 | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-71090 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-71090 |