CVE-2026-23053
Deadlock Vulnerability in Linux Kernel NFSv4.1 Memory Reclamation
Publication date: 2026-02-04
Last updated on: 2026-03-25
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a deadlock issue in the Linux kernel related to the Network File System (NFS), specifically involving the function nfs_release_folio().
The deadlock occurs during NFSv4.1 state recovery when the kernel thread (kthreadd) tries to reclaim memory by calling nfs_release_folio(), but cannot proceed because state recovery is still needed, causing a circular wait.
The fix involves initiating a writeback of the folio without waiting for it to complete or starting an asynchronous commit to avoid the deadlock.
How can this vulnerability impact me? :
This deadlock vulnerability can cause the Linux kernel to hang or become unresponsive during NFSv4.1 state recovery operations.
Such a deadlock may lead to system performance degradation, potential service interruptions, or inability to reclaim memory properly, which could affect applications relying on NFS.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know