data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-46256 in the interactive tracker

CVE-2026-46256

NFS/localio: prevent direct reclaim recursion into NFS via nfs_writepages

EPSS 0.1%

Published 2026-06-03 (5 months ago) by the Linux kernel CNA. Subsystem fs/nfs. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-46256 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed6.18.14-1Update the kernel and reboot. Fixed in 6.18.14-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.18.14-1Update the kernel and reboot. Fixed in 6.18.14-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

LOCALIO is an NFS loopback mount optimization that avoids using the network for READ, WRITE and COMMIT if the NFS client and server are determined to be on the same system. But because LOCALIO is still fundamentally "just NFS loopback mount" it is susceptible to recursion deadlock via direct reclaim, e.g.: NFS LOCALIO down to XFS and then back into NFS via nfs_writepages. Fix LOCALIO's potential for direct reclaim deadlock by ensuring that all its page cache allocations are done from GFP_NOFS context. Thanks to Ben Coddington for pointing out commit ad22c7a043c2 ("xfs: prevent stack overflows from page cache allocation").

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

fs/nfs/localio.c

What this is
NFS, SUNRPC, AND LOCKD CLIENTSMAINTAINERS section matched on fs/nfs/ · linux-nfs@vger.kernel.org · Maintained

Check it on the machine

grep -wE 'CONFIG_NFS_FS|CONFIG_NFS_LOCALIO' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code in 3 releases. The build rule could not be established for 1 release, so nothing is claimed about those.

  • bookworm?
  • trixie, forky, sidn
?
not established - no Makefile entry for the affected file
n
not enabled on any flavour - this release does not build the code

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

Build switches
CONFIG_NFS_FS, CONFIG_NFS_LOCALIO
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-06-03 (5 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.13%, higher than 2.6% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
fs/nfs

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.126.18.14ae26a4cf2baf
6.126.19.46a5de0c4fc0f
6.127.067435d2d8a33

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-46256, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.