dm flakey: don't corrupt the zero page
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a00f5276e26636cbf72f24f79831026d2e2868e7 · < be360c83f2d810493c04f999d69ec9152981e0c0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
dm flakey: don't corrupt the zero page
When we need to zero some range on a block device, the function __blkdev_issue_zero_pages submits a write bio with the bio vector pointing to the zero page. If we use dm-flakey with corrupt bio writes option, it will corrupt the content of the zero page which results in crashes of various userspace programs. Glibc assumes that memory returned by mmap is zeroed and it uses it for calloc implementation; if the newly mapped memory is not zeroed, calloc will return non-zeroed memory.
Fix this bug by testing if the page is equal to ZERO_PAGE(0) and avoiding the corruption in this case.
From the CVE record · Linux
The Linux kernel’s dm-flakey corrupt-bio-writes option can modify the shared zero page when a block-device zeroing operation uses it. This can crash userspace programs or cause calloc to return memory that is not zeroed. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels that use dm-flakey with the corrupt-bio-writes option should check whether their kernel is affected; no affected versions are specified.