f2fs: fix information leak in f2fs_move_inline_dirents()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4ec17d688d74b6b7cb10043c57ff4818cde2b0ca · < f07a8d61b6ea81bb3cbe0638af40f8824d6147fd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix information leak in f2fs_move_inline_dirents()
When converting an inline directory to a regular one, f2fs is leaking uninitialized memory to disk because it doesn't initialize the entire directory block. Fix this by zero-initializing the block.
This bug was introduced by commit 4ec17d688d74 ("f2fs: avoid unneeded initializing when converting inline dentry"), which didn't consider the security implications of leaking uninitialized memory to disk.
This was found by running xfstest generic/435 on a KMSAN-enabled kernel.
From the CVE record · Linux
When f2fs converts an inline directory to a regular one, it can write uninitialized memory to disk because it does not initialize the entire directory block. This may expose kernel memory to someone able to read the affected disk data; the input does not specify authentication or user-interaction requirements.
Teams running Linux kernels with f2fs should check their kernel versions; affected versions are not specified in the input.