- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 8 days later
· 8 days later
Published
- 10 months later
· 10 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (9 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 – < 66eb53cecc5f83183535bbfb2fa6464322049b61
- affected dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 – < edb2b255618621dc83d0ec23150e16b2c697077f
- affected dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 – < 9c0960ed112398bdb6c60ccf6e6b583bc59acede
- affected dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 – < 49e7347f4644d031306d56cb4d51e467cbdcbc69
- affected dc0b9435238c1a68150c798c9c7a1b5d7414cbb9 – < 2c5f4a53476e3cab70adc77b38942c066bd2c17c
- affected 6.6
- unaffected < 6.6
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.63 – ≤ 6.12.*
- unaffected 6.17.13 – ≤ 6.17.*
- unaffected 6.18.2 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
5
- https://git.kernel.org/stable/c/66eb53cecc5f83183535bbfb2fa6464322049b61 (opens in a new tab)
- https://git.kernel.org/stable/c/edb2b255618621dc83d0ec23150e16b2c697077f (opens in a new tab)
- https://git.kernel.org/stable/c/9c0960ed112398bdb6c60ccf6e6b583bc59acede (opens in a new tab)
- https://git.kernel.org/stable/c/49e7347f4644d031306d56cb4d51e467cbdcbc69 (opens in a new tab)
- https://git.kernel.org/stable/c/2c5f4a53476e3cab70adc77b38942c066bd2c17c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-205098 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68356)Record last updated .