# CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio()

> A deadlock in the Linux kernel NFS module can cause a denial of service during memory reclamation and state recovery.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2026
- **Updated:** 11 May 2026
- **Also known as:** AZL-77157, BELL-CVE-2026-23053, DEBIAN-CVE-2026-23053, GHSA-89rw-2v88-2798, ROOT-OS-DEBIAN-13-CVE-2026-23053, ROOT-OS-UBUNTU-2404-CVE-2026-23053, UBUNTU-CVE-2026-23053

## What is CVE-2026-23053?

CVE-2026-23053 is a denial of service vulnerability in Linux, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-23053?


## How do I fix CVE-2026-23053?

Apply the vendor's patch.

## Is CVE-2026-23053 being exploited?

There is no known exploitation of CVE-2026-23053 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23053 and fix it if it is affected.

What it is: CVE-2026-23053 is a denial of service vulnerability in Linux, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23053 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23053/ (Markdown: https://insights.sbomify.com/CVE-2026-23053/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23053
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23053
- OSV: https://osv.dev/vulnerability/CVE-2026-23053

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23053/
Summaries are generated and may contain mistakes; the official description above is the record.