ext4: regenerate buddy after block freeing failed if under fc replay
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6bd97bf273bdb4944904e57480f6545bca48ad77 · < c9b528c35795b711331ed36dc3dbee90d5812d4e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: regenerate buddy after block freeing failed if under fc replay
This mostly reverts commit 6bd97bf273bd ("ext4: remove redundant mb_regenerate_buddy()") and reintroduces mb_regenerate_buddy(). Based on code in mb_free_blocks(), fast commit replay can end up marking as free blocks that are already marked as such. This causes corruption of the buddy bitmap so we need to regenerate it in that case.
From the CVE record · Linux
The Linux kernel’s ext4 code can corrupt its buddy bitmap during fast commit replay if it tries to free blocks already marked free. The input does not establish how an attacker could trigger this or whether network access, authentication, local access, or user interaction is required.
Teams running Linux kernels with ext4 should check whether their versions are affected; no affected versions are listed in the input.