VulnerabilityPublished 24 Dec 2025Updated 21 Oct 2026

CVE-2025-68356: Linux kernel · gfs2: Prevent recursive memory reclaim

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in edb2b255618621dc83d0ec23150e16b2c697077f : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in edb2b255618621dc83d0ec23150e16b2c697077f, 66eb53cecc5f83183535bbfb2fa6464322049b61, 49e7347f4644d031306d56cb4d51e467cbdcbc69 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ dc0b9435238c1a68150c798c9c7a1b5d7414cbb9, < edb2b255618621dc83d0ec23150e16b2c697077f	Fixed in edb2b255618621dc83d0ec23150e16b2c697077f
LinuxLinux	Affected ≥ dc0b9435238c1a68150c798c9c7a1b5d7414cbb9, < 66eb53cecc5f83183535bbfb2fa6464322049b61	Fixed in 66eb53cecc5f83183535bbfb2fa6464322049b61
LinuxLinux	Affected ≥ dc0b9435238c1a68150c798c9c7a1b5d7414cbb9, < 49e7347f4644d031306d56cb4d51e467cbdcbc69	Fixed in 49e7347f4644d031306d56cb4d51e467cbdcbc69
LinuxLinux	Affected ≥ dc0b9435238c1a68150c798c9c7a1b5d7414cbb9, < 9c0960ed112398bdb6c60ccf6e6b583bc59acede	Fixed in 9c0960ed112398bdb6c60ccf6e6b583bc59acede
LinuxLinux	Affected ≥ dc0b9435238c1a68150c798c9c7a1b5d7414cbb9, < 2c5f4a53476e3cab70adc77b38942c066bd2c17c	Fixed in 2c5f4a53476e3cab70adc77b38942c066bd2c17c
LinuxLinux	Affected =6.6	Fixed in–

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.

References

Community reviews

Loading reviews…