---
id: CVE-2026-46256
title: 'NFS/localio: prevent direct reclaim recursion into NFS via nfs_writepages'
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

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

  LOCALIO is an NFS loopback mount optimization that avoids using the
  network for READ, WRITE a…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 <
    9118e1cab8a5571c6a95011f77ff28480aee9cb0
  - >-
    Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 <
    ae26a4cf2baf0a44c538dc093504d1994b02dade
  - >-
    Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 <
    6a5de0c4fc0f217eea945d3d72c34ee30d72cbc9
  - >-
    Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 <
    67435d2d8a33a75f9647724952cb1b18279d2e95
  - Linux 6.12
published: '2026-06-03'
updated: '2026-10-21'
sourceUpdated: '2026-10-21T12:41:32.006Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-46256'
references:
  - url: 'https://git.kernel.org/stable/c/9118e1cab8a5571c6a95011f77ff28480aee9cb0'
  - url: 'https://git.kernel.org/stable/c/ae26a4cf2baf0a44c538dc093504d1994b02dade'
  - url: 'https://git.kernel.org/stable/c/6a5de0c4fc0f217eea945d3d72c34ee30d72cbc9'
  - url: 'https://git.kernel.org/stable/c/67435d2d8a33a75f9647724952cb1b18279d2e95'
tags:
  - cve.org
epss: 0.00134
epssPercentile: 0.02578
ingestedAt: '2026-10-21T12:48:53.627Z'
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

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

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").

## Affected

- `Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 < 9118e1cab8a5571c6a95011f77ff28480aee9cb0`
- `Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 < ae26a4cf2baf0a44c538dc093504d1994b02dade`
- `Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 < 6a5de0c4fc0f217eea945d3d72c34ee30d72cbc9`
- `Linux >= 70ba381e1a431245c137ed597ec6a05991c79bd9 < 67435d2d8a33a75f9647724952cb1b18279d2e95`
- `Linux 6.12`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.