CVE-2025-40242: gfs2: Fix unlikely race in gdlm_put_lock
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 279bde3bbb0ac0bad5c729dfa85983d75a5d7641, 28c4d9bc0708956c1a736a9e49fee71b65deee81, 4.10.
Low priority for now. Upgrade to Linux Linux 279bde3bbb0ac0bad5c729dfa85983d75a5d7641, 28c4d9bc0708956c1a736a9e49fee71b65deee81, 4.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 4, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6aa628c45875e7b8cca81ed9447a12a0e8f3504a, a97e75203733be0a4263a78fb7b29352be150c1c, 3554b46204e67333e1fb8be0e93936fb08267c80, 5cff77b9827a956d076168b56775aad23bce87e4, 8deedce385d220f90e435f534d71d27526273515, 2225a5cd2fbc2ef0e0f78e585db3844f60416a39, 02e838963fdaa6ce8570b5389aecdc6cf1fb40b0, 01eb3106f43335fdc02111358dae80a5c3fd324d, 5.15affected
- d1340f80f0b8066321b499a376780da00560e857 and later · before 5fdc1474e678eea1700aa266c0b7c2c96f81dd0daffected · git
- d1340f80f0b8066321b499a376780da00560e857 and later · before 4913592a3358f6ec366b8346b733d5e2360b08e1affected · git
- d1340f80f0b8066321b499a376780da00560e857 and later · before 279bde3bbb0ac0bad5c729dfa85983d75a5d7641affected · git
- d1340f80f0b8066321b499a376780da00560e857 and later · before 64c61b4ac645222fa7b724cef616c1f862a72a40affected · git
- d1340f80f0b8066321b499a376780da00560e857 and later · before 28c4d9bc0708956c1a736a9e49fee71b65deee81affected · git
- 4.4.284 and later · before 4.5affected · semver
- 4.9.283 and later · before 4.10affected · semver
- 4.14.247 and later · before 4.15affected · semver
- 4.19.207 and later · before 4.20affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
+85
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-40240Dec 4, 2025 · sctp: avoid NULL dereference when chunk data buffer is missing30Monitor
- ← EarlierCVE-2025-40241Dec 4, 2025 · erofs: fix crafted invalid cases for encoded extents31Monitor
- Later →CVE-2025-40243Dec 4, 2025 · hfs: fix KMSAN uninit-value issue in hfs_find_set_zero_bits()31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 279bde3bbb0ac0bad5c729dfa85983d75a5d7641 | Vendor (CNA) |
| Linux Linux | 28c4d9bc0708956c1a736a9e49fee71b65deee81 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4913592a3358f6ec366b8346b733d5e2360b08e1 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 5.15 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5fdc1474e678eea1700aa266c0b7c2c96f81dd0d | Vendor (CNA) |
| Linux Linux | 64c61b4ac645222fa7b724cef616c1f862a72a40 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.171.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.171.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-rt | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
+22
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.