CVE-2025-38659
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Linux Kernel < 6.6.102
- Linux Kernel < 6.12.42
- Linux Kernel < 6.15.10
- Linux Kernel < 6.16.1
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38659.md and follow it. Check whether this project is affected by CVE-2025-38659. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1a91ba12abef628b43cada87478328274d988e88
- https://git.kernel.org/stable/c/6784367b2f3cd7b89103de35764f37f152590dbd
- https://git.kernel.org/stable/c/97c94c7dbddc34d353c83b541b3decabf98d04af
- https://git.kernel.org/stable/c/deb016c1669002e48c431d6fd32ea1c20ef41756
- https://git.kernel.org/stable/c/f5426ffbec971a8f7346a57392d3a901bdee5a9b
References
- https://git.kernel.org/stable/c/1a91ba12abef628b43cada87478328274d988e88
- https://git.kernel.org/stable/c/6784367b2f3cd7b89103de35764f37f152590dbd
- https://git.kernel.org/stable/c/69cf5699a402ee7ae1be53954dc2ae652c0a053c
- https://git.kernel.org/stable/c/6ebe17b359bead383581f729e43f591c1c36e159
- https://git.kernel.org/stable/c/97c94c7dbddc34d353c83b541b3decabf98d04af
- https://git.kernel.org/stable/c/deb016c1669002e48c431d6fd32ea1c20ef41756
- https://git.kernel.org/stable/c/f5426ffbec971a8f7346a57392d3a901bdee5a9b