CVE-2025-40242 — gfs2: Fix unlikely race in gdlm_put_lock
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+1
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 02e838963fdaa6ce8570b5389aecdc6cf1fb40b0version 5.15≥ 5.14.6 and < 5.15≥ 5.13.19 and < 5.14≥ 5.10.67 and < 5.11≥ 5.4.148 and < 5.5≥ 4.19.207 and < 4.20≥ 4.14.247 and < 4.15 and 14 more≥ 4.9.283 and < 4.10≥ 4.4.284 and < 4.5version 01eb3106f43335fdc02111358dae80a5c3fd324d≥ d1340f80f0b8066321b499a376780da00560e857 and < 5fdc1474e678eea1700aa266c0b7c2c96f81dd0dversion 2225a5cd2fbc2ef0e0f78e585db3844f60416a39version 8deedce385d220f90e435f534d71d27526273515version 5cff77b9827a956d076168b56775aad23bce87e4version 3554b46204e67333e1fb8be0e93936fb08267c80version a97e75203733be0a4263a78fb7b29352be150c1cversion 6aa628c45875e7b8cca81ed9447a12a0e8f3504a≥ d1340f80f0b8066321b499a376780da00560e857 and < 28c4d9bc0708956c1a736a9e49fee71b65deee81≥ d1340f80f0b8066321b499a376780da00560e857 and < 64c61b4ac645222fa7b724cef616c1f862a72a40≥ d1340f80f0b8066321b499a376780da00560e857 and < 279bde3bbb0ac0bad5c729dfa85983d75a5d7641≥ d1340f80f0b8066321b499a376780da00560e857 and < 4913592a3358f6ec366b8346b733d5e2360b08e1 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.0 | CVSS 3.1 | High | 1.0 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.0 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.0 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.15%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.0
- Source status changed · → Deferred
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
7 on the record
- nvd.nist.gov/vuln/detail/CVE-2025-40242
- git.kernel.org/stable/c/5fdc1474e678eea1700aa266c0b7c2c96f81dd0d
- git.kernel.org/stable/c/4913592a3358f6ec366b8346b733d5e2360b08e1
- github.com/advisories/GHSA-4g8j-hwjq-h8fr
- git.kernel.org/stable/c/64c61b4ac645222fa7b724cef616c1f862a72a40
- git.kernel.org/stable/c/28c4d9bc0708956c1a736a9e49fee71b65deee81
- git.kernel.org/stable/c/279bde3bbb0ac0bad5c729dfa85983d75a5d7641
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 15h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 15h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-40242 is "gfs2: Fix unlikely race in gdlm_put_lock", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.0 describes technical severity. EPSS 0.15% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.