CVE-2026-23053
Unknown Unknown - Not Provided

Deadlock Vulnerability in Linux Kernel NFSv4.1 Memory Reclamation

Vulnerability report for CVE-2026-23053, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-02-04

Last updated on: 2026-03-25

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a deadlock involving nfs_release_folio() Wang Zhaolong reports a deadlock involving NFSv4.1 state recovery waiting on kthreadd, which is attempting to reclaim memory by calling nfs_release_folio(). The latter cannot make progress due to state recovery being needed. It seems that the only safe thing to do here is to kick off a writeback of the folio, without waiting for completion, or else kicking off an asynchronous commit.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-02-04
Last Modified
2026-03-25
Generated
2026-07-26
AI Q&A
2026-02-04
EPSS Evaluated
2026-07-25
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

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.

Detection Guidance

I don't know

Impact Analysis

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.

Compliance Impact

I don't know

Mitigation Strategies

I don't know

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-23053. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart