CVE-2025-68356gfs2: Prevent recursive memory reclaim
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: gfs2: Prevent recursive memory reclaim Function new_inode() returns a new inode with inode->i_mapping->gfp_mask set to GFP_HIGHUSER_MOVABLE. This value includes the __GFP_FS flag, so allocations in that address space can recurse into filesystem memory reclaim. We don't want that to happen because it can consume a significant amount of stack memory. Worse than that is that it can also deadlock: for example, in several places, gfs2_unstuff_dinode() is called inside filesystem transactions. This calls filemap_grab_folio(), which can allocate a new folio, which can trigger memory reclaim. If memory reclaim recurses into the filesystem and starts another transaction, a deadlock will ensue. To fix these kinds of problems, prevent memory reclaim from recursing into filesystem code by making sure that the gfp_mask of inode address spaces doesn't include __GFP_FS. The "meta" and resource group address spaces were already using GFP_NOFS as their gfp_mask (which doesn't include __GFP_FS). The default value of GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though. To avoid being overly limiting, use the default value and only knock off the __GFP_FS flag. I'm not sure if this will actually make a difference, but it also shouldn't hurt. This patch is loosely based on commit ad22c7a043c2 ("xfs: prevent stack overflows from page cache allocation"). Fixes xfstest generic/273.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Deferred
- Record last updated
- Oct 21, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 before 66eb53cecc5f83183535bbfb2fa6464322049b61; from dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 before edb2b255618621dc83d0ec23150e16b2c697077f; from dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 before 9c0960ed112398bdb6c60ccf6e6b583bc59acede; from dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 before 49e7347f4644d031306d56cb4d51e467cbdcbc69; from dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 before 2c5f4a53476e3cab70adc77b38942c066bd2c17c | CNA record |
References
- https://git.kernel.org/stable/c/66eb53cecc5f83183535bbfb2fa6464322049b61
- https://git.kernel.org/stable/c/edb2b255618621dc83d0ec23150e16b2c697077f
- https://git.kernel.org/stable/c/9c0960ed112398bdb6c60ccf6e6b583bc59acede
- https://git.kernel.org/stable/c/49e7347f4644d031306d56cb4d51e467cbdcbc69
- https://git.kernel.org/stable/c/2c5f4a53476e3cab70adc77b38942c066bd2c17c
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.