CVE-2023-53796
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
The Linux kernel's f2fs filesystem leaks uninitialized memory to disk when converting an inline directory due to missing zero-initialization, allowing possible information disclosure.
Vulnerability
Details The vulnerability resides in f2fs_move_inline_dentrs() within the Linux kernel's f2fs filesystem. When converting an inline directory to a regular one, the function fails to zero-initialize the entire directory block before writing it to disk. This is a regression introduced by commit 4ec17d688d74 ("f2fs: avoid unneeded initializing when converting inline dentry"), which inadvertently removed initialization, leading to uninitialized memory being leaked to disk [1].
Attack
Vector Exploitation requires the ability to trigger conversion of an inline directory on an f2fs filesystem. This can be achieved by creating and then moving a sufficient number of directory entries to exceed the inline capacity, causing the kernel to convert the directory. No special privileges beyond standard file system operations are needed, but the attacker must have write access to the filesystem. The leak occurs during the conversion process, which is triggered by user-space operations.
Impact
The uninitialized memory may contain sensitive kernel heap data. When written to disk, this data persists and could be read by an attacker with access to the raw block device or through a subsequent read of the directory content. This constitutes an information disclosure vulnerability that could expose secrets such as kernel addresses or other sensitive data.
Mitigation
The fix was applied in Linux kernel commits that zero-initialize the directory block before writing. Users should update their kernels to include the fix. The vulnerability was discovered via KMSAN (Kernel Memory Sanitizer) while running xfstest generic/435.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
84e3b4b170bd4a6807ef0f3b32bef8314fcf900b558732662117d4f6687b1f07a8d61b6eaeebaecef00959a5571cff4ffVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/00b5587326625d0fddb2a5f5a3d4acd950102acenvd
- git.kernel.org/stable/c/117d4f6687b1f74423b5d398ea95c63b262a8e73nvd
- git.kernel.org/stable/c/2bef8314fcf94ddc27e22d03f237c0fafd00de33nvd
- git.kernel.org/stable/c/4e3b4b170bd43db1d8a93a6bd0ea434b17cc86f7nvd
- git.kernel.org/stable/c/9a5571cff4ffcfc24847df9fd545cc5799ac0ee5nvd
- git.kernel.org/stable/c/a6807ef0f3b3d8508d3b07a2e35de8a91820a014nvd
- git.kernel.org/stable/c/eebaecef0095bb8f493c03982da75c6e7bae1056nvd
- git.kernel.org/stable/c/f07a8d61b6ea81bb3cbe0638af40f8824d6147fdnvd
News mentions
0No linked articles in our index yet.