Bug 2418819 (CVE-2025-40242) - CVE-2025-40242 kernel: gfs2: Fix unlikely race in gdlm_put_lock
Summary: CVE-2025-40242 kernel: gfs2: Fix unlikely race in gdlm_put_lock
Keywords:
Status: NEW
Alias: CVE-2025-40242
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-04 16:02 UTC by OSIDB Bzimport
Modified: 2026-10-05 11:23 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:75746 0 None None None 2026-10-05 10:48:33 UTC
Red Hat Product Errata RHSA-2026:75747 0 None None None 2026-10-05 11:23:38 UTC

Description OSIDB Bzimport 2025-12-04 16:02:12 UTC
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.

Comment 5 Jon Orris 2026-10-05 10:48:32 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75746 https://access.redhat.com/errata/RHSA-2026:75746

Comment 6 Jon Orris 2026-10-05 11:23:37 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75747 https://access.redhat.com/errata/RHSA-2026:75747


Note You need to log in before you can comment on or make changes to this bug.