Skip to content
Heist/ feed
Back to feed
UnratedFix available

gfs2: Prevent recursive memory reclaim

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.63, 6.17.13, 6.18.2, 6.6.160
CVEs
CVE-2025-68356
Confirmed fixed CVEs
Not specified
Updated in this feed
8 Nov 2026, 00:36 UTC · Revision 1

Source evidence

gfs2: Prevent recursive memory reclaim

core-osv · Original source

Published 24 Dec 2025, 10:32 UTC

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.

osv:CVE-2025-68356

Kernel

Fixed versions: 6.6.160, 6.12.63, 6.17.13, 6.18.2

Complete source record
{
  "id": "a8a4102b62711618e22bff0e05137276f605b3f81666714eda9db12e5a0a0d19",
  "url": "https://osv.dev/vulnerability/CVE-2025-68356",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "gfs2: Prevent recursive memory reclaim",
    "summary": "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.",
    "evidence": "osv:CVE-2025-68356",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.6.160",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.63",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.17.13",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.2",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-68356",
      "aliases": [
        "CVE-2025-68356"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "dc0b9435238c1a68150c798c9c7a1b5d7414cbb9"
                },
                {
                  "fixed": "66eb53cecc5f83183535bbfb2fa6464322049b61"
                },
                {
                  "fixed": "edb2b255618621dc83d0ec23150e16b2c697077f"
                },
                {
                  "fixed": "9c0960ed112398bdb6c60ccf6e6b583bc59acede"
                },
                {
                  "fixed": "49e7347f4644d031306d56cb4d51e467cbdcbc69"
                },
                {
                  "fixed": "2c5f4a53476e3cab70adc77b38942c066bd2c17c"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68356.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.6.0"
                },
                {
                  "fixed": "6.6.160"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.63"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.17.13"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.18.0"
                },
                {
                  "fixed": "6.18.2"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-68356.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:52.304869859Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/2c5f4a53476e3cab70adc77b38942c066bd2c17c",
        "https://git.kernel.org/stable/c/49e7347f4644d031306d56cb4d51e467cbdcbc69",
        "https://git.kernel.org/stable/c/66eb53cecc5f83183535bbfb2fa6464322049b61",
        "https://git.kernel.org/stable/c/9c0960ed112398bdb6c60ccf6e6b583bc59acede",
        "https://git.kernel.org/stable/c/edb2b255618621dc83d0ec23150e16b2c697077f",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68356.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-68356",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68356.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-68356",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 521019,
  "published_at": "2025-12-24T10:32:46.275+00:00"
}