CVE-2025-38659gfs2: No more self recovery
- 7.8HighCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 4 months later
· 4 months later
Published
- 14 months later
· 14 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 601ef0d52e9617588fcff3df26953592f2eb44ac – < 69cf5699a402ee7ae1be53954dc2ae652c0a053c
- affected 601ef0d52e9617588fcff3df26953592f2eb44ac – < 6ebe17b359bead383581f729e43f591c1c36e159
- affected 601ef0d52e9617588fcff3df26953592f2eb44ac – < 1a91ba12abef628b43cada87478328274d988e88
- affected 601ef0d52e9617588fcff3df26953592f2eb44ac – < f5426ffbec971a8f7346a57392d3a901bdee5a9b
- affected 601ef0d52e9617588fcff3df26953592f2eb44ac – < 6784367b2f3cd7b89103de35764f37f152590dbd
- affected 601ef0d52e9617588fcff3df26953592f2eb44ac – < 97c94c7dbddc34d353c83b541b3decabf98d04af
- affected 601ef0d52e9617588fcff3df26953592f2eb44ac – < deb016c1669002e48c431d6fd32ea1c20ef41756
- affected 5.7
- unaffected < 5.7
- unaffected 5.15.209 – ≤ 5.15.*
- unaffected 6.1.167 – ≤ 6.1.*
- unaffected 6.6.102 – ≤ 6.6.*
- unaffected 6.12.42 – ≤ 6.12.*
- unaffected 6.15.10 – ≤ 6.15.*
- unaffected 6.16.1 – ≤ 6.16.*
- unaffected 6.17 – ≤ *
References
References7
- https://git.kernel.org/stable/c/69cf5699a402ee7ae1be53954dc2ae652c0a053c (opens in a new tab)
- https://git.kernel.org/stable/c/6ebe17b359bead383581f729e43f591c1c36e159 (opens in a new tab)
- https://git.kernel.org/stable/c/1a91ba12abef628b43cada87478328274d988e88 (opens in a new tab)
- https://git.kernel.org/stable/c/f5426ffbec971a8f7346a57392d3a901bdee5a9b (opens in a new tab)
- https://git.kernel.org/stable/c/6784367b2f3cd7b89103de35764f37f152590dbd (opens in a new tab)
- https://git.kernel.org/stable/c/97c94c7dbddc34d353c83b541b3decabf98d04af (opens in a new tab)
- https://git.kernel.org/stable/c/deb016c1669002e48c431d6fd32ea1c20ef41756 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-25543 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-38659)Record last updated .