NFS/localio: prevent direct reclaim recursion into NFS via nfs_writepages
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.114, 6.18.14, 6.19.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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 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").
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 70ba381e1a431245c137ed597ec6a05991c79bd9 · fixed in 9118e1cab8a5571c6a95011f77ff28480aee9cb0; From 70ba381e1a431245c137ed597ec6a05991c79bd9 · fixed in ae26a4cf2baf0a44c538dc093504d1994b02dade; From 70ba381e1a431245c137ed597ec6a05991c79bd9 · fixed in 6a5de0c4fc0f217eea945d3d72c34ee30d72cbc9; From 70ba381e1a431245c137ed597ec6a05991c79bd9 · fixed in 67435d2d8a33a75f9647724952cb1b18279d2e95
- Linux Linux
6.12
- KernelLinux
From 6.12.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.14; From 6.19.0 · fixed in 6.19.4