fs/ntfs3: Initialize new folios before use
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Initialize new folios before use
KMSAN reports an uninitialized value in longest_match_std(), invoked from ntfs_compress_write(). When new folios are allocated without being marked uptodate and ni_read_frame() is skipped because the caller expects the frame to be completely overwritten, some reserved folios may remain only partially filled, leaving the rest memory uninitialized.
From the CVE record · Linux
The Linux kernel's fs/ntfs3 code can use uninitialized memory during NTFS compressed writes. This occurs when newly allocated folios are not marked uptodate, a frame read is skipped, and some reserved folios remain partially filled. The input does not specify an attacker action, access requirements, or user interaction.
Engineers running Linux kernels with fs/ntfs3 should check their kernel's status; affected versions are not specified.