CVE-2024-38570

gfs2: Fix potential glock use-after-free on unmount

State
Published
Severity
9.8 Critical
Published
Jun 19, 2024
Updated
Oct 30, 2026
Reserved
Jun 18, 2024

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.19.8 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 to before 94b32a85d1a76ae4f1b42a88677fa20b20187729Affected
  • fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 to before 0636b34b44589b142700ac137b5f69802cfe2e37Affected
  • fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 to before e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0Affected
  • fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 to before 501cd8fabf621d10bd4893e37f6ce6c20523c8caAffected
  • fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 to before d98779e687726d8f8860f1c54b5687eec5f63a73Affected
LinuxLinux
  • 3.8Affected
  • before 3.8Not affected
  • 6.1.191 through 6.1.*Not affected
  • 6.6.33 through 6.6.*Not affected
  • 6.8.12 through 6.8.*Not affected
  • 6.9.3 through 6.9.*Not affected
  • 6.10 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.