fs/ntfs3: Initialize allocated memory before use
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 82cae269cfa953032fbb8980a7d554d60fb00b17 · < a8a3ca23bbd9d849308a7921a049330dc6c91398| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Initialize allocated memory before use
KMSAN reports: Multiple uninitialized values detected:
- KMSAN: uninit-value in ntfs_read_hdr (3) - KMSAN: uninit-value in bcmp (3)
Memory is allocated by __getname(), which is a wrapper for kmem_cache_alloc(). This memory is used before being properly cleared. Change kmem_cache_alloc() to kmem_cache_zalloc() to properly allocate and clear memory before use.
From the CVE record · Linux
The Linux kernel’s fs/ntfs3 code uses allocated memory before clearing it, causing uninitialized-value reports in ntfs_read_hdr and bcmp. The input does not establish what an attacker could do or specify whether exploitation requires network or local access, authentication, or user interaction.
Engineers running Linux kernels with fs/ntfs3 should check their exposure; affected versions are not specified.