CVE-2026-23050: pNFS: Fix a deadlock when returning a delegation during open()
In the Linux kernel, the following vulnerability has been resolved:
pNFS: Fix a deadlock when returning a delegation during open()
Ben Coddington reports seeing a hang in the following stack trace:
0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415
1 [ffffd0b50e177548] schedule at ffffffff9ca05717
2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1
3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb
4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5
5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]
6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]
7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]
8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]
9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]
10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]
11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]
12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]
13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]
14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]
15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]
16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]
17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea
18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e
19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935
The issue is that the delegreturn is being asked to wait for a layout
return that cannot complete because a state recovery was initiated. The
state recovery cannot complete until the open() finishes processing the
delegations it was given.
The solution is to propagate the existing flags that indicate a
non-blocking call to the function pnfs_roc(), so that it knows not to
wait in this situation.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23050 is a Linux kernel flaw in the NFSv4/pNFS client path that can cause a system hang during file open handling. The public record describes a deadlock, not data theft or remote code execution. Business urgency is highest for systems that rely on NFSv4/pNFS for critical file access or availability.
Executive priority
Treat as a targeted availability risk. Patch during normal or accelerated maintenance for NFS-dependent servers, clusters, and storage clients. It is not currently supported by sources as an emergency remote-compromise issue.
Technical view
The issue occurs when a delegation return waits for a pNFS layout return that cannot complete because state recovery is blocked until open() finishes processing delegations. The fix propagates existing non-blocking flags into pnfs_roc() so it does not wait in this condition. Public sources list Linux kernel impact and stable kernel commits resolving it.
Likely exposure
Exposure is most likely on Linux systems using NFSv4 with pNFS/delegation behavior, especially file clients handling open() operations against NFS infrastructure. Systems not using NFSv4/pNFS are less likely to encounter the vulnerable path. Exact distribution package impact must be checked with each Linux vendor.
Exploitation context
The provided sources describe a deadlock and kernel hang scenario. They do not report active exploitation, public exploit code, CVSS scoring, or KEV listing. Impact appears availability-focused and dependent on specific NFS client state conditions rather than broad unauthenticated compromise.
Researcher notes
Evidence is limited to the CVE description and Linux stable commit references. No CWE, CVSS, exploit status, or distribution-specific package matrix is provided. Analysis should focus on NFSv4/pNFS client code paths and whether local workloads can trigger the described delegation-return deadlock.
Mitigation direction
Prioritize updates for Linux systems that use NFSv4 or pNFS in production.
Apply vendor kernel updates that include the referenced stable fixes.
Check distribution advisories for exact affected package versions and backports.
Consider operational monitoring for NFS client hangs until patched.
Validation and detection
Inventory Linux hosts that mount or depend on NFSv4/pNFS shares.
Compare running kernel builds against vendor advisories and fixed stable commits.
Review incident logs for unexplained NFS client hangs during file open activity.
Confirm patched kernels are deployed after maintenance.
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-2026-23050 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 4, 2026, 16:04 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.