VDB

CVE-2025-22025

CVE-2025-22025 PUBLISHED CVSS 7.5 HIGH

nfsd: put dl_stid if fail to queue dl_recall

Reported by linux · Published April 16, 2025

In the Linux kernel, the following vulnerability has been resolved: nfsd: put dl_stid if fail to queue dl_recall Before calling nfsd4_run_cb to queue dl_recall to the callback_wq, we increment the reference count of dl_stid. We expect that after the corresponding work_struct is processed, the reference count of dl_stid will be decremented through the callback function nfsd4_cb_recall_release. However, if the call to nfsd4_run_cb fails, the incremented reference count of dl_stid will not be decremented correspondingly, leading to the following nfs4_stid leak: unreferenced object 0xffff88812067b578 (size 344): comm "nfsd", pid 2761, jiffies 4295044002 (age 5541.241s) hex dump (first 32 bytes): 01 00 00 00 6b 6b 6b 6b b8 02 c0 e2 81 88 ff ff ....kkkk........ 00 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 ad 4e ad de .kkkkkkk.....N.. backtrace: kmem_cache_alloc+0x4b9/0x700 nfsd4_process_open1+0x34/0x300 nfsd4_open+0x2d1/0x9d0 nfsd4_proc_compound+0x7a2/0xe30 nfsd_dispatch+0x241/0x3e0 svc_process_common+0x5d3/0xcc0 svc_process+0x2a3/0x320 nfsd+0x180/0x2e0 kthread+0x199/0x1d0 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1b/0x30 unreferenced object 0xffff8881499f4d28 (size 368): comm "nfsd", pid 2761, jiffies 4295044005 (age 5541.239s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 30 4d 9f 49 81 88 ff ff ........0M.I.... 30 4d 9f 49 81 88 ff ff 20 00 00 00 01 00 00 00 0M.I.... ....... backtrace: kmem_cache_alloc+0x4b9/0x700 nfs4_alloc_stid+0x29/0x210 alloc_init_deleg+0x92/0x2e0 nfs4_set_delegation+0x284/0xc00 nfs4_open_delegation+0x216/0x3f0 nfsd4_process_open2+0x2b3/0xee0 nfsd4_open+0x770/0x9d0 nfsd4_proc_compound+0x7a2/0xe30 nfsd_dispatch+0x241/0x3e0 svc_process_common+0x5d3/0xcc0 svc_process+0x2a3/0x320 nfsd+0x180/0x2e0 kthread+0x199/0x1d0 ret_from_fork+0x30/0x50 ret_from_fork_asm+0x1b/0x30 Fix it by checking the result of nfsd4_run_cb and call nfs4_put_stid if fail to queue dl_recall.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.12Amazon Linux6.12.23-29.97.amzn2023
python3-perf6.12Amazon Linux6.12.23-29.97.amzn2023
kernel-livepatch-6.1.134-150.224Amazon Linux1.0-0.amzn2023
bpftoolAmazon Linux6.1.134-150.224.amzn2023
kernelAmazon Linux6.1.134-150.224.amzn2023
perfAmazon Linux6.1.134-150.224.amzn2023
kernel-develAmazon Linux6.1.134-150.224.amzn2023
kernel-headersAmazon Linux6.1.134-150.224.amzn2023
perf6.12Amazon Linux6.12.23-29.97.amzn2023
kernel-libbpf-staticAmazon Linux6.1.134-150.224.amzn2023
kernel-libbpfAmazon Linux6.1.134-150.224.amzn2023
kernel6.12-modules-extraAmazon Linux6.12.23-29.97.amzn2023

4 more packages have a fixed version. See every fix in Lookup.

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

VendorProductVersions
LinuxLinuxb5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf
LinuxLinux2.6.35, 0, 5.10.236
amazon:2023kernel6.120
amazon:2023python3-perf6.120
amazon:2023kernel-livepatch-6.1.134-150.2240
amazon:2023bpftool0
amazon:2023kernel0
amazon:2023perf0
amazon:2023kernel-devel0
amazon:2023kernel-headers0
amazon:2023perf6.120
amazon:2023kernel-libbpf-static0
amazon:2023kernel-libbpf0
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel-modules-extra-common0
amazon:2023kernel-livepatch-6.12.23-29.970
LinuxLinux*, 6.15, 5.10.236
amazon:2023kernel-modules-extra0
linuxlinux_kernel2.6.35, 2.6.35, 2.6.35
amazon:2023python3-perf0

…and 3 more

Timeline

  • Apr 16, 2025 CVE Published
  • Apr 17, 2025 EPSS Score (30 in total, the first dated here)
  • May 30, 2025 Coalition ESS Score (17 in total, the first dated here)
  • Dec 21, 2025 Security Advisory (325 in total, the first dated here)
  • Apr 20, 2026 Distribution Patch (318 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-22025
vulnetix vdb fixes CVE-2025-22025

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-22025/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›