Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-40242gfs2: Fix unlikely race in gdlm_put_lock

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.

Timeline

  1. ID reserved

    By Linux

  2. · 8 months later

    Published

  3. · 11 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-40242, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.0.

Affected products

  • Linux · Linux

    • affected d1340f80f0b8066321b499a376780da00560e857 – < 5fdc1474e678eea1700aa266c0b7c2c96f81dd0d
    • affected d1340f80f0b8066321b499a376780da00560e857 – < 4913592a3358f6ec366b8346b733d5e2360b08e1
    • affected d1340f80f0b8066321b499a376780da00560e857 – < 279bde3bbb0ac0bad5c729dfa85983d75a5d7641
    • affected d1340f80f0b8066321b499a376780da00560e857 – < 64c61b4ac645222fa7b724cef616c1f862a72a40
    • affected d1340f80f0b8066321b499a376780da00560e857 – < 28c4d9bc0708956c1a736a9e49fee71b65deee81
    • affected 6aa628c45875e7b8cca81ed9447a12a0e8f3504a
    • affected a97e75203733be0a4263a78fb7b29352be150c1c
    • affected 3554b46204e67333e1fb8be0e93936fb08267c80
    • affected 5cff77b9827a956d076168b56775aad23bce87e4
    • affected 8deedce385d220f90e435f534d71d27526273515
    • affected 2225a5cd2fbc2ef0e0f78e585db3844f60416a39
    • affected 02e838963fdaa6ce8570b5389aecdc6cf1fb40b0
    • affected 01eb3106f43335fdc02111358dae80a5c3fd324d
    • affected 4.4.284 – < 4.5
    • affected 4.9.283 – < 4.10
    • affected 4.14.247 – < 4.15
    • affected 4.19.207 – < 4.20
    • affected 5.4.148 – < 5.5
    • affected 5.10.67 – < 5.11
    • affected 5.13.19 – < 5.14
    • affected 5.14.6 – < 5.15
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.56 – ≤ 6.12.*
    • unaffected 6.17.6 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40242 badge
[![CVE-2025-40242](https://cveledger.app/badge/CVE-2025-40242.svg)](https://cveledger.app/cve/CVE-2025-40242)

Record last updated .