CVE-2024-38570: Linux kernel · gfs2: Fix potential glock use-after-free on unmount
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical · fixed in 4.4.0-1136.142 : patch Linux kernel as a priority.
Data as of 28 Oct 2026, 10:59 UTC
- Patch
- Available – fixed in 4.4.0-1136.142, 4.15.0-1181.196~14.04.1, 4.4.0-259.293~14.04.1 +95
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7021-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7022-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7021-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7021-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7039-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7022-2 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-38570 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-38570 (opens in a new tab)
- git.kernel.org/linus/d98779e687726d8f8860f1c54b5687eec5f63a73 (opens in a new tab)
- git.kernel.org/stable/c/0636b34b44589b142700ac137b5f69802cfe2e37 (opens in a new tab)
- git.kernel.org/stable/c/e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0 (opens in a new tab)
- git.kernel.org/stable/c/501cd8fabf621d10bd4893e37f6ce6c20523c8ca (opens in a new tab)
- git.kernel.org/stable/c/d98779e687726d8f8860f1c54b5687eec5f63a73 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6955-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-6949-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-6952-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7021-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7022-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7021-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7021-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7039-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7022-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7021-4 (opens in a new tab)