CVE-2025-40242
BaseFortify
Publication date: 2025-12-04
Last updated on: 2026-04-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in the Linux kernel's gfs2 filesystem code, specifically in the gdlm_put_lock() function. There is a small time window where the DFL_UNMOUNT flag is set but the lockspace has not yet been released. During this window, the distributed lock manager (dlm) may still call functions that dereference glock objects that have been freed, potentially leading to use-after-free errors. The fix ensures that glock objects are only freed if the lockspace has actually been released, preventing dereferencing freed objects.
How can this vulnerability impact me? :
This vulnerability could lead to kernel instability or crashes due to dereferencing freed memory objects in the filesystem lock management code. Such instability could cause system downtime or data corruption in environments using the gfs2 filesystem with distributed locking.