f2fs: fix to tag gcing flag on page during block migration
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to tag gcing flag on page during block migration
It needs to add missing gcing flag on page during block migration, in order to garantee migrated data be persisted during checkpoint, otherwise out-of-order persistency between data and node may cause data corruption after SPOR.
Similar issue was fixed by commit 2d1fe8a86bf5 ("f2fs: fix to tag gcing flag on page during file defragment").
From the CVE record · Linux
The Linux kernel’s f2fs block migration can fail to mark a page with the gcing flag, allowing data and node information to persist out of order. This may cause data corruption after SPOR. The input does not specify an attacker action, access requirements, or user interaction.
Teams running Linux kernels that use f2fs should check whether their kernel includes the fix; affected versions are not specified.