{"schema_version":"1.9.0","id":"CVE-2024-38570","published":"2024-06-19T13:35:36.274Z","modified":"2026-08-12T03:51:25.623097046Z","related":["ALSA-2024:6997","ALSA-2024:7000","ALSA-2024:7001","SUSE-SU-2024:2571-1","SUSE-SU-2024:2894-1","SUSE-SU-2024:2896-1","SUSE-SU-2024:2939-1","SUSE-SU-2024:2947-1","SUSE-SU-2024:2973-1","SUSE-SU-2025:20008-1","SUSE-SU-2025:20028-1"],"summary":"gfs2: Fix potential glock use-after-free on unmount","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix potential glock use-after-free on unmount\n\nWhen a DLM lockspace is released and there ares still locks in that\nlockspace, DLM will unlock those locks automatically.  Commit\nfb6791d100d1b started exploiting this behavior to speed up filesystem\nunmount: gfs2 would simply free glocks it didn't want to unlock and then\nrelease the lockspace.  This didn't take the bast callbacks for\nasynchronous lock contention notifications into account, which remain\nactive until until a lock is unlocked or its lockspace is released.\n\nTo prevent those callbacks from accessing deallocated objects, put the\nglocks that should not be unlocked on the sd_dead_glocks list, release\nthe lockspace, and only then free those glocks.\n\nAs an additional measure, ignore unexpected ast and bast callbacks if\nthe receiving glock is dead.","affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"fb6791d100d1bba20b5cdbc4912e1f7086ec60f8"},{"fixed":"0636b34b44589b142700ac137b5f69802cfe2e37"},{"fixed":"e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0"},{"fixed":"501cd8fabf621d10bd4893e37f6ce6c20523c8ca"},{"fixed":"d98779e687726d8f8860f1c54b5687eec5f63a73"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-38570.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.8.0"},{"fixed":"6.6.33"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.8.12"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.9.0"},{"fixed":"6.9.3"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-38570.json"}}],"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/0636b34b44589b142700ac137b5f69802cfe2e37"},{"type":"WEB","url":"https://git.kernel.org/stable/c/501cd8fabf621d10bd4893e37f6ce6c20523c8ca"},{"type":"WEB","url":"https://git.kernel.org/stable/c/d98779e687726d8f8860f1c54b5687eec5f63a73"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38570.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38570"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/38xxx/CVE-2024-38570.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}]}