ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 163a203ddb36c36d4a1c942aececda0cc8d06aa7 · < 0184747b552d6b5a14db3b7fcc3b792ce64dedd1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()
Determine if the group block bitmap is corrupted before using ac_b_ex in ext4_mb_try_best_found() to avoid allocating blocks from a group with a corrupted block bitmap in the following concurrency and making the situation worse.
ext4_mb_regular_allocator ext4_lock_group(sb, group) ext4_mb_good_group // check if the group bbitmap is corrupted ext4_mb_complex_scan_group // Scan group gets ac_b_ex but doesn't use it ext4_unlock_group(sb, group) ext4_mark_group_bitmap_corrupted(group) // The block bitmap was corrupted during // the group unlock gap. ext4_mb_try_best_found ext4_lock_group(ac->ac_sb, group) ext4_mb_use_best_found mb_mark_used // Allocating blocks in block bitmap corrupted group
From the CVE record · Linux
The Linux kernel’s ext4 allocator can allocate blocks from a group whose block bitmap becomes corrupted between checks. This requires a concurrent bitmap-corruption event; the input does not specify an attacker access requirement or user interaction.
Engineers running Linux systems that use ext4 should check their kernel; affected versions were not provided.