LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22025: nfsd: put dl_stid if fail to queue dl_recall

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux kernel NFS server can leak kernel memory when an NFS delegation-recall task cannot be queued. Repeated failures could consume resources and disrupt availability. The supplied CVSS score is 7.5, but the sources provide no evidence of data theft, modification, or active exploitation.

Executive priority

Prioritize externally reachable or business-critical NFS servers for prompt vendor-supported kernel updates. The expected impact is service degradation or outage rather than confidentiality loss. Avoid declaring an emergency solely from the score because active exploitation and reliable triggering are not demonstrated.

Technical view

The NFS server increments the dl_stid reference count before queuing dl_recall work. If nfsd4_run_cb fails, the callback that normally releases the reference never runs, leaving an nfs4_stid allocation leaked. The documented fix checks the queueing result and calls nfs4_put_stid on failure.

Likely exposure

Exposure is concentrated on systems running affected Linux kernels with the kernel NFS server active. Network-accessible NFS servers warrant priority. Systems not providing NFS service are unlikely to reach this code path. The supplied version data is ambiguous, so confirm affected and fixed packages with each distribution vendor.

Exploitation context

The CVSS vector characterizes the issue as remotely reachable, low complexity, unauthenticated, and availability-only. However, the bundle contains no proof-of-concept, reported attacks, or CISA KEV listing. Whether an attacker can reliably force the required callback-queue failure is not established by the supplied evidence.

Researcher notes

The failure is a reference-count leak in the delegation-recall callback error path, supported by kernel leak traces. The stable commits show a narrowly scoped release-on-queue-failure correction. No CWE was supplied. Exact vulnerable ranges, practical trigger reliability, and exploit prevalence remain insufficiently documented in the bundle.

Mitigation direction

  • Inventory Linux systems providing kernel NFS service and record their running kernel packages.
  • Apply a distribution-supported kernel update containing the documented NFS reference-release fix.
  • Consult distribution advisories for exact fixed package versions and backport status.
  • Reboot affected systems when required so the corrected kernel is actually running.
  • If updates are delayed, follow vendor guidance and limit NFS access to necessary trusted clients.

Validation and detection

  • Confirm whether the kernel NFS server is enabled and serving network clients.
  • Compare each running kernel package against the relevant distribution security advisory.
  • Verify the installed kernel includes the nfsd4_run_cb failure-path reference-release fix.
  • Confirm the corrected kernel is running after maintenance or reboot.
  • Review monitoring for unexplained nfsd-related memory growth or resource exhaustion.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22025 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-22025Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcf, b5a1a81e5c25fb6bb3fdc1812ba69ff6ab638fcfunaffected
LinuxLinux2.6.35, 0, 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.