CVE-2026-46256
Direct reclaim deadlock in Linux kernel NFS LOCALIO
Publication date: 2026-06-03
Last updated on: 2026-06-03
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 exists in the Linux kernel's NFS LOCALIO feature, which is an optimization that allows NFS clients and servers on the same system to avoid using the network for certain operations like READ, WRITE, and COMMIT.
Because LOCALIO is essentially an NFS loopback mount, it is vulnerable to a recursion deadlock caused by direct reclaim. Specifically, this can happen when NFS LOCALIO operations go down to the XFS filesystem and then back into NFS through the nfs_writepages function.
The issue is fixed by ensuring that all page cache allocations in LOCALIO are done from the GFP_NOFS context, which prevents the direct reclaim recursion deadlock.
How can this vulnerability impact me? :
This vulnerability can cause a recursion deadlock in the Linux kernel when using NFS LOCALIO, potentially leading to system hangs or degraded performance during file operations involving NFS and XFS.
Such deadlocks can affect system stability and availability, especially on systems relying on NFS LOCALIO for optimized local file access.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability in the Linux kernel related to NFS LOCALIO causing potential direct reclaim recursion deadlock has been fixed by ensuring all page cache allocations are done from GFP_NOFS context.
To mitigate this vulnerability immediately, you should update your Linux kernel to a version that includes this fix.