CVE-2025-40242

gfs2: Fix unlikely race in gdlm_put_lock

HIGH
7
CVSS Score
Published: December 4, 2025 at 03:31 PM UTC
Updated: October 19, 2026 at 07:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix unlikely race in gdlm_put_lock In gdlm_put_lock(), there is a small window of time in which the DFL_UNMOUNT flag has been set but the lockspace hasn't been released, yet. In that window, dlm may still call gdlm_ast() and gdlm_bast(). To prevent it from dereferencing freed glock objects, only free the glock if the lockspace has actually been released.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

01eb3106f43335fdc02111358dae80a5c3fd324d02e838963fdaa6ce8570b5389aecdc6cf1fb40b01eb3106f43335fdc2111358dae80a5c3fd324d2225a5cd2fbc2ef0e0f78e585db3844f60416a392e838963fdaa6ce8570b5389aecdc6cf1fb40b03554b46204e67333e1fb8be0e93936fb08267c804.14.2474.19.2074.4.2844.9.2835.10.675.13.195.14.65.155.4.1485cff77b9827a956d076168b56775aad23bce87e46aa628c45875e7b8cca81ed9447a12a0e8f3504a8deedce385d220f90e435f534d71d27526273515a97e75203733be0a4263a78fb7b29352be150c1cd1340f80f0b8066321b499a376780da00560e857
Vendor states this is fixed in 279bde3bbb0ac0bad5c729dfa85983d75a5d7641 (fixed)
Vendor states this is fixed in 28c4d9bc0708956c1a736a9e49fee71b65deee81 (fixed)
Vendor states this is fixed in 4913592a3358f6ec366b8346b733d5e2360b08e1 (fixed)
Vendor states this is fixed in 5fdc1474e678eea1700aa266c0b7c2c96f81dd0d (fixed)
Vendor states this is fixed in 64c61b4ac645222fa7b724cef616c1f862a72a40 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.14, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.15 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.168 (unaffected)
Vendor states this is fixed in 6.12.56 (unaffected)
Vendor states this is fixed in 6.17.6 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.131 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card