f2fs: remove clear SB_INLINECRYPT flag in default_options
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 · < ac5eecf481c29942eb9a862e758c0c8b68090c33| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: remove clear SB_INLINECRYPT flag in default_options
In f2fs_remount, SB_INLINECRYPT flag will be clear and re-set. If create new file or open file during this gap, these files will not use inlinecrypt. Worse case, it may lead to data corruption if wrappedkey_v0 is enable.
Thread A: Thread B:
-f2fs_remount -f2fs_file_open or f2fs_new_inode -default_options <- clear SB_INLINECRYPT flag
-fscrypt_select_encryption_impl
-parse_options <- set SB_INLINECRYPT again
From the CVE record · Linux
During an f2fs remount, the kernel briefly clears the inline-encryption flag. A file created or opened during that gap may not use inline encryption, potentially causing data corruption if wrappedkey_v0 is enabled. The input does not specify whether an attacker can trigger the race or what access they would need.
Engineers running Linux systems with f2fs should check their kernel versions; affected versions are not specified.