CVE-2025-68356
Recursive Memory Reclaim Vulnerability in Linux GFS2 Causes Deadlock
Publication date: 2025-12-24
Last updated on: 2025-12-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
| linux | kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's gfs2 filesystem involves recursive memory reclaim caused by the gfp_mask flag GFP_HIGHUSER_MOVABLE including the __GFP_FS flag. This allows memory allocations to recurse into filesystem memory reclaim, which can consume significant stack memory and potentially cause deadlocks during filesystem transactions. The issue arises when functions like gfs2_unstuff_dinode() trigger memory reclaim that recurses into the filesystem, starting another transaction and causing a deadlock. The fix prevents memory reclaim from recursing into filesystem code by removing the __GFP_FS flag from the gfp_mask of inode address spaces.
How can this vulnerability impact me? :
This vulnerability can lead to significant stack memory consumption and deadlocks within the filesystem during memory allocation and reclaim operations. Such deadlocks can cause system hangs or crashes, impacting system stability and availability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your Linux kernel to a version that includes the patch preventing recursive memory reclaim in gfs2. This patch modifies the gfp_mask of inode address spaces to exclude the __GFP_FS flag, preventing deadlocks and excessive stack memory consumption. Applying the official kernel update or patch that fixes this issue is the recommended immediate step.