CVE-2025-38659
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…
Does this matter?
Lower severity and a low EPSS score (0.17%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.17% probability · 6th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-476
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/1a91ba12abef628b43cada87478328274d988e88Patch
- https://git.kernel.org/stable/c/6784367b2f3cd7b89103de35764f37f152590dbdPatch
- https://git.kernel.org/stable/c/69cf5699a402ee7ae1be53954dc2ae652c0a053c
- https://git.kernel.org/stable/c/6ebe17b359bead383581f729e43f591c1c36e159
- https://git.kernel.org/stable/c/97c94c7dbddc34d353c83b541b3decabf98d04afPatch
- https://git.kernel.org/stable/c/deb016c1669002e48c431d6fd32ea1c20ef41756Patch
- https://git.kernel.org/stable/c/f5426ffbec971a8f7346a57392d3a901bdee5a9bPatch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.