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-2024-38570gfs2: Fix potential glock use-after-free on unmount

Description

In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix potential glock use-after-free on unmount When a DLM lockspace is released and there ares still locks in that lockspace, DLM will unlock those locks automatically. Commit fb6791d100d1b started exploiting this behavior to speed up filesystem unmount: gfs2 would simply free glocks it didn't want to unlock and then release the lockspace. This didn't take the bast callbacks for asynchronous lock contention notifications into account, which remain active until until a lock is unlocked or its lockspace is released. To prevent those callbacks from accessing deallocated objects, put the glocks that should not be unlocked on the sd_dead_glocks list, release the lockspace, and only then free those glocks. As an additional measure, ignore unexpected ast and bast callbacks if the receiving glock is dead.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 2 years 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-2024-38570, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.68% · top 47% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 – < 94b32a85d1a76ae4f1b42a88677fa20b20187729
    • affected fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 – < 0636b34b44589b142700ac137b5f69802cfe2e37
    • affected fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 – < e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0
    • affected fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 – < 501cd8fabf621d10bd4893e37f6ce6c20523c8ca
    • affected fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 – < d98779e687726d8f8860f1c54b5687eec5f63a73
  • Linux · Linux

    • affected 3.8
    • unaffected < 3.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.33 – ≤ 6.6.*
    • unaffected 6.8.12 – ≤ 6.8.*
    • unaffected 6.9.3 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .