CVE-2026-23053

UnknownEPSS 0.17%

Last modified

CVE-2026-23053 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 96780ca55e3cbf4f150fd5a833a61492c9947b5b, < a4810f8beb0122f032f10735f98d257aa6064f4c; >= 96780ca55e3cbf4f150fd5a833a61492c9947b5b, < 49d352bc263fe4a834233338bfaad31b3109addf; >= 96780ca55e3cbf4f150fd5a833a61492c9947b5b, < 19b4d9ab5e77843eac0429c019470c02f8710b55; >= 96780ca55e3cbf4f150fd5a833a61492c9947b5b, < cce0be6eb4971456b703aaeafd571650d314bcca
LinuxLinux6.3

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2026-23053?
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.
How severe is CVE-2026-23053?
Severity scoring for CVE-2026-23053 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-23053?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-23053?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST