ntfs: treat any nonzero dio zero-range return as an error
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:
ntfs: treat any nonzero dio zero-range return as an error
ntfs_dio_zero_range() returns either 0 or a negative errno from blkdev_issue_zeroout(); it never returns a positive value. The zeroing failure check in ntfs_attr_fallocate() therefore never fired, so a failed zeroing operation was silently ignored: the loop kept going, the newly allocated clusters were folded into initialized_size and the write could succeed leaving stale on-disk data.
Treat any nonzero return as an error and abort the allocation.
From the CVE record · Linux
The Linux kernel's NTFS allocation path could ignore a failed zeroing operation and report a successful write, leaving stale data on disk. This can occur when zeroing fails during allocation; the input does not specify attacker access or user-interaction requirements.
Engineers running Linux kernels with NTFS support should check their kernel; affected versions are not specified.