CVE-2025-38659

gfs2: No more self recovery

State
Published
Severity
7.8 High
Published
Aug 22, 2025
Updated
Oct 15, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 601ef0d52e9617588fcff3df26953592f2eb44ac to before 69cf5699a402ee7ae1be53954dc2ae652c0a053cAffected
  • 601ef0d52e9617588fcff3df26953592f2eb44ac to before 6ebe17b359bead383581f729e43f591c1c36e159Affected
  • 601ef0d52e9617588fcff3df26953592f2eb44ac to before 1a91ba12abef628b43cada87478328274d988e88Affected
  • 601ef0d52e9617588fcff3df26953592f2eb44ac to before f5426ffbec971a8f7346a57392d3a901bdee5a9bAffected
  • 601ef0d52e9617588fcff3df26953592f2eb44ac to before 6784367b2f3cd7b89103de35764f37f152590dbdAffected
  • 601ef0d52e9617588fcff3df26953592f2eb44ac to before 97c94c7dbddc34d353c83b541b3decabf98d04afAffected
  • 601ef0d52e9617588fcff3df26953592f2eb44ac to before deb016c1669002e48c431d6fd32ea1c20ef41756Affected
LinuxLinux
  • 5.7Affected
  • before 5.7Not affected
  • 5.15.209 through 5.15.*Not affected
  • 6.1.167 through 6.1.*Not affected
  • 6.6.102 through 6.6.*Not affected
  • 6.12.42 through 6.12.*Not affected
  • 6.15.10 through 6.15.*Not affected
  • 6.16.1 through 6.16.*Not affected
  • 6.17 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.