Answer in brief
CVE-2024-38570 records a Unknown severity vulnerability in gfs2: Fix potential glock use-after-free on unmount. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <0636b34b44589b142700ac137b5f69802cfe2e37 || >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0 || >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <501cd8fabf621d10bd4893e37f6ce6c20523c8ca || >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <d98779e687726d8f8860f1c54b5687eec5f63a73 | 0636b34b44589b142700ac137b5f69802cfe2e37, e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0, 501cd8fabf621d10bd4893e37f6ce6c20523c8ca, d98779e687726d8f8860f1c54b5687eec5f63a73 |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Jun 19, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-38570 records a Unknown severity vulnerability in gfs2: Fix potential glock use-after-free on unmount. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <0636b34b44589b142700ac137b5f69802cfe2e37 || >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0 || >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <501cd8fabf621d10bd4893e37f6ce6c20523c8ca || >=fb6791d100d1bba20b5cdbc4912e1f7086ec60f8 <d98779e687726d8f8860f1c54b5687eec5f63a73 | 0636b34b44589b142700ac137b5f69802cfe2e37, e42e8a24d7f02d28763d16ca7ec5fc6d1f142af0, 501cd8fabf621d10bd4893e37f6ce6c20523c8ca, d98779e687726d8f8860f1c54b5687eec5f63a73 |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Jun 19, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.