CVE-2025-22025: nfsd: put dl_stid if fail to queue dl_recall
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 133f5e2a37ce08c82d24e8fba65e0a81deae4609, 230ca758453c63bd38e4d9f4a21db698f7abada8, 63b91c8ff4589f5263873b24c052447a28e10ef7; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 133f5e2a37ce08c82d24e8fba65e0a81deae4609, 230ca758453c63bd38e4d9f4a21db698f7abada8, 63b91c8ff4589f5263873b24c052447a28e10ef7; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 16, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- CWE-401
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.5
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.35affected
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before b874cdef4e67e5150e07eff0eae1cbb21fb92da1affected · git
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before cdb796137c57e68ca34518d53be53b679351eb86affected · git
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before d96587cc93ec369031bcd7658c6adc719873c9fdaffected · git
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before 9a81cde8c7ce65dd90fb47ceea93a45fc1a2fbd1affected · git
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before cad3479b63661a399c9df1d0b759e1806e2df3c8affected · git
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before 63b91c8ff4589f5263873b24c052447a28e10ef7affected · git
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before 133f5e2a37ce08c82d24e8fba65e0a81deae4609affected · git
- b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf and later · before 230ca758453c63bd38e4d9f4a21db698f7abada8affected · git
- before 2.6.35not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.10.236
- linux linux kernel5.11 and later · before 5.15.180
- linux linux kernel5.16 and later · before 6.1.134
- linux linux kernel6.2 and later · before 6.6.87
- linux linux kernel6.7 and later · before 6.12.23
- linux linux kernel6.13 and later · before 6.13.11
- linux linux kernel6.14 and later · before 6.14.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.135-1 | 6.1.135-1 |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-58093Apr 16, 2025 · PCI/ASPM: Fix link state exit during switch upstream function removal31Monitor
- ← EarlierCVE-2024-58096Apr 16, 2025 · wifi: ath11k: add srng->lock for ath11k_hal_srng_* in monitor mode22Monitor
- Later →CVE-2025-22037Apr 16, 2025 · ksmbd: fix null pointer dereference in alloc_preauth_hash()51Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 133f5e2a37ce08c82d24e8fba65e0a81deae4609 | Vendor (CNA) |
| Linux Linux | 230ca758453c63bd38e4d9f4a21db698f7abada8 | Vendor (CNA) |
| Linux Linux | 63b91c8ff4589f5263873b24c052447a28e10ef7 | Vendor (CNA) |
| Linux Linux | 9a81cde8c7ce65dd90fb47ceea93a45fc1a2fbd1 | Vendor (CNA) |
| Linux Linux | b874cdef4e67e5150e07eff0eae1cbb21fb92da1 | Vendor (CNA) |
| Linux Linux | cad3479b63661a399c9df1d0b759e1806e2df3c8 | Vendor (CNA) |
| Linux Linux | cdb796137c57e68ca34518d53be53b679351eb86 | Vendor (CNA) |
| Linux Linux | d96587cc93ec369031bcd7658c6adc719873c9fd | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.135-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/230ca758453c63bd38e4d9f4a21db698f7abada8
- git.kernel.org/stable/c/63b91c8ff4589f5263873b24c052447a28e10ef7
- git.kernel.org/stable/c/9a81cde8c7ce65dd90fb47ceea93a45fc1a2fbd1
- git.kernel.org/stable/c/b874cdef4e67e5150e07eff0eae1cbb21fb92da1
- git.kernel.org/stable/c/cad3479b63661a399c9df1d0b759e1806e2df3c8
- git.kernel.org/stable/c/cdb796137c57e68ca34518d53be53b679351eb86
- git.kernel.org/stable/c/d96587cc93ec369031bcd7658c6adc719873c9fd
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.