VDB

CVE-2025-68356

CVE-2025-68356 PUBLISHED

gfs2: Prevent recursive memory reclaim

Reported by linux · Published December 24, 2025

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.

EPSS 0.22% · 13.1th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinux9c0960ed112398bdb6c60ccf6e6b583bc59acede, 66eb53cecc5f83183535bbfb2fa6464322049b61, 6.6, 49e7347f4644d031306d56cb4d51e467cbdcbc69, 2c5f4a53476e3cab70adc77b38942c066bd2c17c

Risk scores

EPSS Score
0.22%
13.1th percentile

Affected products

VendorProductVersions
LinuxLinuxdc0b9435238c1a68150c798c9c7a1b5d7414cbb9, dc0b9435238c1a68150c798c9c7a1b5d7414cbb9, dc0b9435238c1a68150c798c9c7a1b5d7414cbb9
LinuxLinux6.6, 0, 6.6.160
LinuxLinux6.6.160, 6.17.13, 6.6
linuxlinux_kernel6.6, 6.6, 6.6

Timeline

  • Dec 23, 2025 CVE Published
  • Dec 24, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (130 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (135 in total, the first dated here)
  • Jun 17, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-68356
vulnetix vdb fixes CVE-2025-68356

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68356/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›