Answer in brief
CVE-2025-38659 records a Unknown severity vulnerability in gfs2: No more self recovery. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=601ef0d52e9617588fcff3df26953592f2eb44ac <69cf5699a402ee7ae1be53954dc2ae652c0a053c || >=601ef0d52e9617588fcff3df26953592f2eb44ac <6ebe17b359bead383581f729e43f591c1c36e159 || >=601ef0d52e9617588fcff3df26953592f2eb44ac <1a91ba12abef628b43cada87478328274d988e88 || >=601ef0d52e9617588fcff3df26953592f2eb44ac <f5426ffbec971a8f7346a57392d3a901bdee5a9b || >=601ef0d52e9617588fcff3df26953592f2eb44ac <6784367b2f3cd7b89103de35764f37f152590dbd || >=601ef0d52e9617588fcff3df26953592f2eb44ac <97c94c7dbddc34d353c83b541b3decabf98d04af || >=601ef0d52e9617588fcff3df26953592f2eb44ac <deb016c1669002e48c431d6fd32ea1c20ef41756 | 69cf5699a402ee7ae1be53954dc2ae652c0a053c, 6ebe17b359bead383581f729e43f591c1c36e159, 1a91ba12abef628b43cada87478328274d988e88, f5426ffbec971a8f7346a57392d3a901bdee5a9b, 6784367b2f3cd7b89103de35764f37f152590dbd, 97c94c7dbddc34d353c83b541b3decabf98d04af, deb016c1669002e48c431d6fd32ea1c20ef41756 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: gfs2: No more self recovery When a node withdraws and it turns out that it is the only node that has the filesystem mounted, gfs2 currently tries to replay the local journal to bring the filesystem back into a consistent state. Not only is that a very bad idea, it has also never worked because gfs2_recover_func() will refuse to do anything during a withdraw. However, before even getting to this point, gfs2_recover_func() dereferences sdp->sd_jdesc->jd_inode. This was a use-after-free before commit 04133b607a78 ("gfs2: Prevent double iput for journal on error") and is a NULL pointer dereference since then. Simply get rid of self recovery to fix that.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-38659 records a Unknown severity vulnerability in gfs2: No more self recovery. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=601ef0d52e9617588fcff3df26953592f2eb44ac <69cf5699a402ee7ae1be53954dc2ae652c0a053c || >=601ef0d52e9617588fcff3df26953592f2eb44ac <6ebe17b359bead383581f729e43f591c1c36e159 || >=601ef0d52e9617588fcff3df26953592f2eb44ac <1a91ba12abef628b43cada87478328274d988e88 || >=601ef0d52e9617588fcff3df26953592f2eb44ac <f5426ffbec971a8f7346a57392d3a901bdee5a9b || >=601ef0d52e9617588fcff3df26953592f2eb44ac <6784367b2f3cd7b89103de35764f37f152590dbd || >=601ef0d52e9617588fcff3df26953592f2eb44ac <97c94c7dbddc34d353c83b541b3decabf98d04af || >=601ef0d52e9617588fcff3df26953592f2eb44ac <deb016c1669002e48c431d6fd32ea1c20ef41756 | 69cf5699a402ee7ae1be53954dc2ae652c0a053c, 6ebe17b359bead383581f729e43f591c1c36e159, 1a91ba12abef628b43cada87478328274d988e88, f5426ffbec971a8f7346a57392d3a901bdee5a9b, 6784367b2f3cd7b89103de35764f37f152590dbd, 97c94c7dbddc34d353c83b541b3decabf98d04af, deb016c1669002e48c431d6fd32ea1c20ef41756 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Aug 22, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: gfs2: No more self recovery When a node withdraws and it turns out that it is the only node that has the filesystem mounted, gfs2 currently tries to replay the local journal to bring the filesystem back into a consistent state. Not only is that a very bad idea, it has also never worked because gfs2_recover_func() will refuse to do anything during a withdraw. However, before even getting to this point, gfs2_recover_func() dereferences sdp->sd_jdesc->jd_inode. This was a use-after-free before commit 04133b607a78 ("gfs2: Prevent double iput for journal on error") and is a NULL pointer dereference since then. Simply get rid of self recovery to fix that.
Quoted source text, attributed separately from HOL analysis.