gfs2: Fix use-after-free in gfs2_glock_shrink_scan
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7881ef3f33bb80f459ea6020d1e021fc524a6348 · < a61156314b66456ab6a291ed5deba1ebd002ab3c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gfs2: Fix use-after-free in gfs2_glock_shrink_scan
The GLF_LRU flag is checked under lru_lock in gfs2_glock_remove_from_lru() to remove the glock from the lru list in __gfs2_glock_put().
On the shrink scan path, the same flag is cleared under lru_lock but because of cond_resched_lock(&lru_lock) in gfs2_dispose_glock_lru(), progress on the put side can be made without deleting the glock from the lru list.
Keep GLF_LRU across the race window opened by cond_resched_lock(&lru_lock) to ensure correct behavior on both sides - clear GLF_LRU after list_del under lru_lock.
From the CVE record · Linux
A race in the Linux kernel’s GFS2 glock shrink scan can cause a use-after-free when the glock is not removed from the LRU list. The input does not establish how an attacker could trigger the race or whether access or user interaction is required.
Engineers running the Linux kernel with GFS2 should check their installations; affected versions are not specified.